The value of the "Searchable" property is not imported when you import customizations that contain the "Searchable" property in Microsoft Dynamics CRM 3.0

Article ID: 925233 - View products that this article applies to.
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.
Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You have two Microsoft Dynamics CRM 3.0 servers that have hotfix 912061 installed.
  • On the first server, you export customizations that contain the Searchable property for an entity.
  • On the second server, you import the customizations.
In this scenario, the value of the Searchable property in the exported customizations is not imported by the second server.

For example, you export customizations from one Microsoft Dynamics CRM 3.0 server to another, and both servers contain the same entity. However, the Searchable property value for the entity is Yes on the first server, and the same property value for this entity is No on the second server. After you export the customizations, the fields for the entity are still unsearchable.
Note The Searchable property controls which fields are available to be searched when you use the Advanced Find function in Microsoft Dynamics CRM.
Back to the top | Give Feedback

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
(http://support.microsoft.com/kb/927751/ )
Update Rollup 2 is available for Microsoft Dynamics CRM 3.0
Back to the top | Give Feedback

MORE INFORMATION

The value of the Searchable property is not imported into certain fields after you install hotfix 925233. These fields are lookup fields that are used to relate one entity to another entity. These lookup fields are not included in the actual attribute list when the entities customizations .xml file is exported. This behavior is by design because the relationship attribute information is exported in a different section of the customizations .xml file. The Searchable property can only be exported or imported on fields that are valid in the main Microsoft Dynamics CRM form. For example, the accountid field is a primary key. The accountid field and other primary key fields are not valid in the form.

For more information about hotfix 912061, click the following article number to view the article in the Microsoft Knowledge Base:
912061
(http://support.microsoft.com/kb/912061/ )
Some fields are not available as search criteria when you use Advanced Find in Microsoft Dynamics CRM 3.0

Note Hotfix rollup 922815 contains this hotfix.

For more information about hotfix rollup 922815, click the following article number to view the article in the Microsoft Knowledge Base:
922815
(http://support.microsoft.com/kb/922815/ )
Update Rollup 1 for Microsoft Dynamics CRM 3.0 is available
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
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
887283
(http://support.microsoft.com/kb/887283/ )
Microsoft Business Solutions CRM software hotfix and update package naming standards
Back to the top | Give Feedback

Properties

Article ID: 925233 - Last Review: July 17, 2007 - Revision: 3.2
APPLIES TO
  • Microsoft CRM 3.0
Keywords: 
kbhotfixserver kbqfe kbmbsmigrate KB925233
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top