Dynamics CRM 2013 features that are no longer supported

Every time we upgrade the new system, we need to investigate which features can not be used after the upgrade, after all, the system version of the upgrade there is a huge risk: custom development, database data can face the risk of loss. This article is mainly about customizing the development of this piece, see the new version of the system to the old code compatibility.

Dynamics CRM 2011

The new system fully supports custom features developed with support technology and is not supported by features developed in Unsupport mode. I basically do not use unsupport such hack technology for custom development, you know this kind of development is not only difficult to maintain, and once the version of the upgrade and no longer be supported will become helpless.

Unsupport development is also divided into server-side and client-side, the Unsupport development of the server is mainly the direct application system is not developed in the SDK, the new version of the system is likely to refactor these assemblies, so the risk is relatively large. The Unsupport development of the client is mainly to use the original JS directly to the system form to modify, many names are hard code inside, to know that the new version of the system will also refactor the structure of the client, once the refactoring, all JS will be invalidated.

Dynamics CRM 4.0

The new system will not support CRM4.0 code at all: Plug-ins, custom workflows, client code, Web service APIs. It can be seen that the new system should completely reconstruct this piece of code, and adopt the 2011 XRM Framework.

Database Scripts

The Dynamics CRM system corresponds to 2 data tables per entity. In the new system, 2 data tables have been integrated into one. If we are not using the entity's view for development at development time, but are directly working on the datasheet, it will cause your script to fail after the upgrade.