Microsoft Dynamics CRM 2011 can be customized by using all the configuration and customization features available in the web client (and described in this guide), and can be extended by using all the methods described in the Microsoft Dynamics CRM software development kit (SDK).
Customizations made by using other methods are unsupported. Unsupported customizations might work initially, but they might not work after updates are applied or the application is upgraded, and these customizations are not supported by Microsoft.
This section describes the most common supported and unsupported customization methods likely to be examined in the MB2-866 exam. For a complete list of supported and unsupported customizations, please refer to the CRM SDK available at http://msdn.microsoft.com/en-us/library/gg328350.aspx.
In addition to the configuration and customization features available in the web client, the following customizations are also supported (using the CRM SDK):
Use of the web services including
DiscoveryService, OrganizationService
, Organization Data Service, SOAP endpoint for web services, andDeploymentService
.Form scripting using the documented objects and methods is available by using the
Xrm.Page.data
andXrm.Page.ui
objects.Ribbon customization using
RibbonDiffXML
to add, remove, or hide ribbon elements.The solution files can be customized by exporting and extracting the
customization.xml
file, and making modifications to theCustomizations.xml
file as long as the file still conforms to theCustomizationsSolution.xsd
schema. Ribbon customization, SiteMap customization, form and dashboard customization using FormXML, and saved query customization, all require this technique.Plugins to handle custom business logic that are developed using the mechanism described in the CRM SDK are supported and upgradeable. Adding the plugins and custom workflow activities to the
%installdir%\server\bin\
folder is not supported for Microsoft Dynamics CRM Online.The custom workflow activities (assemblies) that are developed by using the mechanism described in the CRM SDK and called from the workflow processes, and the ability to edit the XAML workflows, is supported and upgradeable.
Adding the custom web pages to the
<serverroot>\ISV\<ISV name>
folder is supported, but deprecated. This means this method will work for earlier versions of Microsoft Dynamics CRM that have been upgraded, but it is not supported for new deployments.
The following types of customization are not supported:
Modifications or additions to the files in the
www
root directories of Microsoft Dynamics CRM.Modifications to the Microsoft Dynamics CRM website, including the filesystem access control lists.
Use of client certificates.
Modifications to the physical schema of the CRM databases—such as adding or modifying tables, stored procedures or views, and so on—other than adding or updating database indexes.
Creating or updating the records directly in the database by using T-SQL or any other method that is not described in the CRM SDK.
Editing the
Customizations.xml
file within a solution to edit any solution components other than ribbons, forms, SiteMap, or saved queries.