Unsupported Customizations
Modifications to Microsoft CRM that are made without using either the Microsoft CRM SDK or Microsoft CRM tools are not supported, and are not preserved during updates or upgrades of Microsoft CRM. In addition, unsupported modifications might cause problems when you update or upgrade Microsoft CRM. In general, you can avoid update and upgrade issues by not modifying any file that you did not create yourself. (The ISV.config file in the wwwroot\_Resources directory is the only exception to this rule.)
The following is a list of the types of actions that are not supported and could cause upgrade problems:
- Modifications to any .apsx, .css, .htm, .js, .xml, .jpg, or .gif files in the wwwroot directories of Microsoft CRM or Microsoft CRM tools. Microsoft CRM does not check these files for modifications during upgrades and updates, and may overwrite them.
- Modifications to the physical schema of the database. This includes any actions performed against the database without going through Schema Manager. Modifying tables, indexes, stored procedures, or views in the database is unsupported. Adding tables, indexes, stored procedures, or views to the database is also unsupported due to referential integrity or upgrade issues. Any time you make changes to the database without using Schema Manager, you run a great risk of problems occurring during updates and upgrades.
- Referencing any dynamic-link libraries (DLL) other than Microsoft.Crm.Platform.Proxy.dll or Microsoft.Crm.Platform.Types.dll. At this time, Microsoft CRM supports only the Microsoft.Crm.Platform.Proxy and Microsoft.Crm.Platform.Types namespaces and their documented APIs. All other installed files can change at any time, and their use is unsupported.
- Modifications to any of the Microsoft CRM custom forms in Microsoft Outlook, or to .pst files, are unsupported and are not upgradeable.