Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The invariantname property is localized unexpectedly when you customize the statuscode attribute of an entity in Microsoft Dynamics CRM 3.0

The invariantname property is localized unexpectedly when you customize the statuscode attribute of an entity in Microsoft Dynamics CRM 3.0

View products that this article applies to.

Symptoms

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. 
     <state value="0" defaultstatus="1" invariantname="Open">
       <labels>
        <label description="Ouvert" languagecode="1036" />
     </labels>
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. 
     <state value="0" defaultstatus="1" invariantname="Ouvert">
       <labels>
        <label description="Ouvert" languagecode="1036" />
     </labels>
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.

↑ Back to the top

Resolution

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:
927751 Update Rollup 2 is available for Microsoft Dynamics CRM 3.0

↑ Back to the top

More information

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

↑ Back to the top

Keywords: KB923258, kbmbsmigrate, kbqfe, kbhotfixserver, kbmbscustomization

↑ Back to the top

Article Info
Article ID : 923258
Revision : 4
Created on : 8/18/2007
Published on : 8/18/2007
Exists online : False
Views : 429