Hi Team,
I am trying to migrate data from SQL server to Dataverse. Currently, I am migrating data for a many-to-many relationship using Azure Data Factory. I have followed the below steps:
1. Using ADF, imported Table1 - Employee
2. Using ADF, imported Table 2 - Training
3. Using ADF, imported Intermediate table (Employee_Training)
Note: I have created the required intersect table data (GUIDs) in Azure SQL - EmployeeID, TrainingID
In step 3, my ADF has failed because I am not able to provide the Alternative Key in the Sink configuration. Please note Employee & Training tables relationship is System many-to-many relationship and not the manual many-to-many relationship, so I don't have access to the table to create an Alternative Key.
ErrorCode=DynamicsMissingKeyColumns,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=,Source=,''Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Input DataSet must contain keycolumn(s) in Upsert/Update scenario. Missing key column(s): pp_training_employeeid
Any workaround? Please advise.
Thank you!
I have also found one forum saying that the Dataverse many-to-many relationship is NOT supported by Azure Data Factory (ADF). Does anyone aware of this limitation with ADF when it comes to Dataverse many-to-many relationships?
Hi @bipinshan
Thanks for your response.
Unfortunately, there is only one option for Dataverse Sink step Write Behavior - Upsert. There is no Insert option. Thanks you!
HI @Sandeep009 ,
Can you please change Write behaviour to Insert from Upsert so that key column(s): pp_training_employeeid GUID will be auto generated by the system?
If you are not able to change the Write Behaviour then try adding another column in your source and randomly generate GUID for that column and map it to pp_training_employeeid in ADF.
Thanks,
Bipin
WarrenBelz
637
Most Valuable Professional
stampcoin
570
Super User 2025 Season 2
Power Apps 1919
473