Unique identifier not passing to Dataverse from SQL

(0) Share

Report

Posted on by HFG

516

Hi all,

We are filling Dataverse tables from a SQL database via an ADF pipeline. We want to create the GUID in SQL and pass it to Dataverse so that we have this information stored in SQL. When we use NEWID() to create the unique identifier, Dataverse doesn't take it into account and creates its own. When we do a convert, unique identifier of the ID of the table (for example ID 1 -> GUID 00000000-0000-0100-000000000000) this value is accepted by Dataverse. Obviously, we would rather not use this as it won't be unique.

Does anyone have any suggestions of what is going on and how we can create a real GUID and pass it to Dataverse ?

Thanks

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Ram Prakash Duraisamy 5,593 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

If you want create another field and store that SQL guid for refrence. Else try to use Virtual entity

Was this reply helpful? Yes No
thomasfnorthrup 252 on at

Like (0)

Report

Hello, thanks for reaching out.
Rampprakash is correct, create a unique id field on the SQL table data and store that in a string column on the table in dataverse, then use that as a reference when matching the tables. You can even create an alternate key on that column. You don't want to mess with the system creating GUID's because if you create GUID and then the system creates a record it may recreate the same GUID, highly unlikely but still possible.
Please mark as a solution or give kudos if this helped.
Good luck, have a great day!

Was this reply helpful? Yes No
HFG 516 on at

Like (0)

Report

Hi @thomasfnorthrup @rampprakash ,

Thanks both for you help. We have tried using the ID column of the table for mapping but the pipeline asks us for the GUID (even if it then creates one itself) and fails if we don't provide it. We also need to know the Dataverse GUID for when we are filling tables with LookUp columns so that we can map to the correct line, that's why we'd like to manage it. I feel like we should be able to do this with an alternate key on the ID column, but it is only working when we provide the GUID...maybe we're missing something.

Was this reply helpful? Yes No