You cannot import the customizations from a Microsoft Dynamics CRM 4.0 system that you upgraded to another Microsoft Dynamics CRM 4.0 system that you also upgraded
This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. On a Microsoft Dynamics CRM 3.0 system, you create a custom entity. You export the customizations of this custom entity, and you import the customizations on another Microsoft Dynamics CRM 3.0 system. Then, you update both systems to Microsoft Dynamics CRM 4.0. Next, you update the custom entity on one of the Microsoft Dynamics CRM 4.0 systems. Finally, you try to export the customizations from this Microsoft Dynamics CRM 4.0 system, and you try to import the customizations on the other Microsoft Dynamics CRM 4.0 system. In this scenario, you cannot import the customizations.
This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
949256 Microsoft Dynamics CRM 4.0 updates and hotfixes
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the terminology that is used to describe Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
887283 Microsoft Business Solutions CRM software hotfix and update package naming standards
Article ID: 948043 - Last Review: 01/17/2015 05:34:00 - Revision: 4.0
Microsoft Dynamics CRM 4.0
- kbnosurvey kbarchive kbfix kbautohotfix kbexpertiseinter kbmbscustomization kbmbsmigrate kbqfe kbhotfixserver KB948043