Upgrading Dynamics CRM to the latest and greatest always has some hurdles to overcome and with the new release of Dynamics CRM 2013, things are no different. Some are expected based on the upgrade validation tool, others may come as a surprise.
The discussion here could lead to data loss which isn’t something we want to happen. Here is an overview of the issue:
This scenario is related to an entity that has a look-up to another entity that may not have the “name” for out-of-the-box entities or “new_name” for custom entities filled in. CRM 2011 allows a look-up to an entity that has the blank name field, but 2013 has put a restriction where it is now required for the relationship to stick.
Dynamics CRM below has the account entity with a look-up to a custom entity “Account Blank Out”. The custom entity has two fields: field 1 and name. The name is NOT a required field, but I have included data in the Field 1 just to show the record has some data on it.
Figure 1: The custom entity “Account Blank Out” record with a blank name.
Figure 2: An account with the look-up to the account blank out entity records. Note the blank name.
Once this account record is setup and saved – it is closed out. When the record is re-opened, the “Blank Account” field reverts back to being blank.
During the upgrade process this has the same effect. If there are records coming over from CRM 2011 that have these properties, then the look-up value that transfers over will go away.
The upgrade from 2011 to 2013 can involve several changes to customizations. It is as important to understand what else goes on behind the scenes during the upgrade. Data needs to be a vital part of the consideration for when the upgrade is right for your organization.
To get around this issue it is recommended to create a workflow before the upgrade is done. The purpose of this workflow will be to create some meaningful data to stick into the name field so when the upgrade does take place this field is filled in on ALL records.