We have been trying to use the Configuration Migration Tool to migrate our USD data from one CRM instance to another CRM instance.
We have experienced varying levels of failure. First, the tool was creating a bunch of duplicate records. Now, after clearing all data out of our target environment and trying a couple more times, it almost works but errors out when trying to create some many-to-many relationships. We have an error message like so (some ID's removed for brevity):
2:13 PM AddM2MRelationships - Result: False - Entity: msdyusd_agentscriptaction - Failed to Link N:N relationship associate between msdyusd_agentscriptaction (ID:2718c6b0-c198-e711-8107-c4346bdc92c1) and msdyusd_agentscriptaction (IDs: a5d4b135-4179-e711-8105-5065f38a9b91,d5561971-a1b2-e711-810b-5065f38a9b91,b794f3dc-7fb3-e711-810b-5065f38a9b91), Link Operation Failed with error : Duplicate Record Found for Entity: 10231 with ID: fa6a8927-0af0-e711-8113-5065f38b3291
It seems that a certain "msdyusd_agentscriptaction" (Action Call) entity is failing to create an N:N relationship with other entities of the same type, claiming "duplicate record found for entity" as if that relationship already exists. However, when I go into the CRM UI, these supposed related entities do not show up in the "related records" area of the page. My Unified Service Desk implementation is also not performing as intended because of this lack of relationship.
Has anyone seen this behavior before with the Configuration Migration Tool?