Unanswered

Dataflows looking up to Systemusers table - not mapping at all

(0) Share

Report

Posted on by JasonHoffoLeic

Hi...

I have a table with lookups to the ystem user table in one environment called DEV and i want to migrate the data into TEST. Seems straightforward and i am using Dataflows.

When i map it is complaining that it cannot find the GUID in the system users table that has been migrated from DEV to TEST and the error is correct because if i look at David Smith (for example in DEV) the guid is different than what David Smith is in TEST.

I am using the power query tool. So I need to get the users name from the guid in DEV and then with the users name get the GUID in TEST and then 'patch that GUID into the power query row. So I can get the correct GUID in TEST to migrate.

Has anyone ever had this problem and how did you overcome it ?

This is the error i am getting in Dataflows :

I have read about the alternate key but how would that work if the GUIDS are different ? Or is this the purpose of them ?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Re: Dataflows looking up to Systemusers table - not mapping at all

Hi @JasonHoffoLeic,

As you alluded to, alternate keys is the trick even if the GUIDs are different. Alt Keys defined another way of uniquely identifiying the records/rows apart from the GUID. So create a new alt key, wait and ensure it is active and then create a new Dataflow. It should upsert correctly 🙂
Hope this helps!

Was this reply helpful? Yes No
JasonHoffoLeic 32 on at

Like (0)

Report

Re: Dataflows looking up to Systemusers table - not mapping at all

@EricRegnier - Hi i am still having tremendous problems. Where would i create the Key ? I need some sort of link between my table and the system user table. When i do the migration the users are blank - or if i try and migrate the columns which i need (from the users table) it gives me that error.

Was this reply helpful? Yes No
EricRegnier 8,720 Most Valuable Professional on at

Like (0)

Report

Re: Dataflows looking up to Systemusers table - not mapping at all

Dataflows import a table at a time. You'll need to coordinate the run time of the Dataflows if records depend on each from different table. So run the Dataflow for the parent table first, then the dependent table second. Base on your initial post, you create the alt key on the User (systemuser) table, maybe you can use the email field as the key? Here's how to create alt keys: https://learn.microsoft.com/power-apps/maker/data-platform/define-alternate-keys-portal

What's the error message?

Was this reply helpful? Yes No