Mismatch of Lookup Guid in development vs production environment

(0) Share

Report

Posted on by Community Member

We have a CRM deployment where the Guid values of some lookup records and other entity records are different in production from the values in staging. And this has become a major issue as we have to manually configure lots of components that rely on these Guid's every time we deploy a solution to the production environment.

I'm looking for advice on how to rectify this problem so that we avoid these tedious manual configurations. We thought about replicating the Guid values from production to development but are not sure about the implications.

Any help is greatly appreciated!

Yosief

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

anilambadan 1,160 on at

Like (0)

Report
Copy link

Link copied!

Hi Yosief,

If you are creating the these lookup values in different environments, there is a chance of getting different values in each environments. So you can you DataMigrationUtility which is included with SDK. Its available under SDK\Tools\ConfgurationMigration folder.

Please see the following link to get more information.

https://technet.microsoft.com/en-us/library/dn647421.aspx

https://technet.microsoft.com/en-us/library/dn647419.aspx

thanks

Anil

Was this reply helpful? Yes No
Mahendar Pal 45,095 on at

Like (0)

Report
Copy link

Link copied!

Hi,

First, you should not hard code Guids, if not you should import your data from one environment to another with GUIDs. You can refer: www.powerobjects.com/.../utilizing-guids-for-importing-data-to-multiple-orgs-dynamics-crm

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks Anil. The Configuration Migration Tool (CMT) turned out to be the only way to fix the mismatched Guids. (Sorry HIMBAP, your suggestion did not import the guids as expected)

I've a similar problem with Access Team Templates where the guids in staging are different from production. I tried using the CMT but there is no corresponding entity that appears in the list. I guess it is because it corresponds to one of those 'hidden' system entities.

Any idea on how to deal with guid issues on Access Team templates?

Was this reply helpful? Yes No