Unanswered

Configuration Migration Tool with Lookups to Same Table (Parent Record)

(0) Share

Report

Posted on by MarkTheGreat

I'm new to using the Configuration Migration Tool but am running into an issue. We have a couple of tables with lookups to the same table (for a parent record). One example is the Team table has been modified with a lookup to designate a Parent Team.

When importing the data, it is failing to find the parent, despite it existing in the system. I have verified this against several tables with the same issue, and any lookup that's to the same table as the existing record, fails to find it, even if it does indeed exist in the target system.

Is this a known bug? What is a good workaround. We have to frequently move a lot of data between environments so this is a bit of an issue for me currently.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (0)

Jonathan Manrique 2,687 on at

Like (0)

Report

Hi @MarkTheGreat

Has it ever happened, what I did first was migrate the equipment table, verify that the GUIDs are the same. I understand that you have not created it manually in the environments.

After migrating the devices, recreate the xml of the data migration tool and add the relationship.

Something important is to verify that the GUIDs are the same in the environments, otherwise it will fail.

Was this reply helpful? Yes No
MarkTheGreat 4 on at

Like (0)

Report

Thank you for your response. As mentioned, the parent team already does exist (under the same GUID in both the source and target environments). I understand I'd need the parent team there first under the same GUID as the source environment before importing the child team.

So I'm not sure why it's failing to find it. It seems to only be an issue if the lookup is to the same table (other lookups work fine, it's only the columns that are a lookup to the same table)

Just to clarify, I am importing a Team, which has a lookup to Team (eg "parent team"). The log indicates it is unable to find the team, despite it existing with the GUID being used. This is repeatable for other tables with a similar situation.

Any other ideas?

Was this reply helpful? Yes No
Jonathan Manrique 2,687 on at

Like (0)

Report

Hi @MarkTheGreat

Use the XRM Tool Box tool and try with this tool

Was this reply helpful? Yes No
MarkTheGreat 4 on at

Like (0)

Report

sorry for the late reply as I was OOO but your response isn't showing a link/screenshot/description of which tool you are suggesting. I know there's a couple (which admittedly I did not try yet)

Was this reply helpful? Yes No