Custom fields prevent activities from being closed when you upgrade from Microsoft CRM 1.2 to Microsoft Dynamics CRM 3.0
This article has been archived. It is offered "as is" and will no longer be updated.
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.
Consider the following scenario. You upgrade from Microsoft CRM 1.2 to Microsoft Dynamics CRM 3.0. Custom fields on the activity tables are created. These fields are created from non-custom fields in Microsoft CRM 1.2. In this scenario, the fields prevent activities from being closed in Microsoft Dynamics CRM 3.0.
This problem occurs because some of the activity fields in Microsoft CRM 1.2 are only used for certain activity types. If fields that are not related to a certain activity type are populated before you upgrade to Microsoft Dynamics CRM 3.0, custom fields are created to retain the data that is stored in the fields.
Examples of these types of fields which can be populated by using the Microsoft CRM 1.2 software development kit (SDK) include the following fields:
This problem is fixed in Microsoft Dynamics CRM 3.0 Update Rollup 1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
922815 Update Rollup 1 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:
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
crm3 crm30 crm3.0
Article ID: 913954 - Last Review: 01/15/2015 08:18:46 - Revision: 4.0
- kbnosurvey kbarchive kbmbsupgrade kbexpertisebeginner kbHotfixServer kbqfe kbmbsmigrate KB913954