When you try to import a customization XML file into Microsoft Dynamics CRM 4.0 or into Microsoft Dynamics CRM 3.0, a SQL Exception error is logged in the Microsoft SQL log. Additionally, the import process fails.
This problem occurs when the customization XML file that you try to import has the same attribute name as the same entity of another customization. However, both customizations have a different case sensitivity property.
This problem occurs because Microsoft Dynamics CRM considers these attributes that have a different case sensitivity property to be different attributes. Therefore, Microsoft Dynamics CRM creates a new attribute instead of updating an attribute.
To resolve this problem, contact Technical Support for Microsoft Dynamics.
For information about technical support for Microsoft Dynamics CRM, visit the following Microsoft Web site:
The support professional will correct the customization XML file.
When you create an attribute in the
Customization area in Microsoft Dynamics CRM, you can type the attribute name in the
Name box. Then, the
Schema Name box populates the name that you typed in the
Name box. The physical name of the attribute is based on the name in the
Schema Name box. However, the case sensitivity property of the physical name is based on the name in the
Name box, unless you change the name in the
Schema Name box. After you click
Save, the case sensitivity property of the physical name is based on the name in the
Schema Name box. Therefore, the physical name is not available for Microsoft Dynamics CRM to update.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.