Article ID: 923258
The hotfix that is discussed in this article is not available for the Chinese version of Microsoft Dynamics CRM or for the Japanese version of Microsoft Dynamics CRM.
When you customize the statuscode attribute of an entity in Microsoft Dynamics CRM 3.0, the invariantname property of the entity is localized unexpectedly.
For example, you are working in the French version of Microsoft Dynamics CRM 3.0. You export the PhoneCall entity in XML format by using the Export Customization tool. You examine the statecode section of the generated XML file to find the collection of status codes that are available. The status codes have an invariantname property and a description property, as shown in the following example.
You change the status code of the entity, and then you publish the changes. When you again examine the content of the generated XML file, the invariantname property is localized, as shown in the following example.
Note If you customize the statuscode property by using the Microsoft Dynamics CRM Software Development Kit (SDK), the invariantname property is used. Additionally, you receive the following error message:
Error 0x80048408: State code is invalid or state code is valid but status code is invalid for a specific state code.
This problem is fixed in Microsoft Dynamics CRM 3.0 Update Rollup 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/927751/ )Update Rollup 2 is available for Microsoft Dynamics CRM 3.0
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:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
(http://support.microsoft.com/kb/887283/ )Microsoft Business Solutions CRM software hotfix and update package naming standards
Article ID: 923258 - Last Review: June 20, 2014 - Revision: 2.0
Contact us for more help