Hello,
I build a user dataverse table using as primary name as the full name of the user. Since we have some homonym, the primary name is not unique. I created an alternate key being the unique identifier of the user which is effectively unique. I am using a dataflow to fill in the dataverse table from a SharePoint list. An upsert using the alternate key was chosen to refresh periodically the user list. The dataflow ran successfully in development for the unmanaged solution. The solution was imported in acceptance as a managed solution and the dataflow executed successfully.
The solution was then imported in production again as a managed solution. But, the dataflow ran in error with the following error for the homonym records ""message":"A record with matching key values already exists.","cdsErrorCode":"0x80040237","InnerErrorMessage":"Cannot insert duplicate key."".
Trying to enter the homonym record directly in the dataverse table, I am getting the following error when entering the full name in the primary column "There was an error in saving this record. A record with matching key values already exists".
I do not understand these errors in production since there is no error in acceptance And, as far as I correctly understood, a primary column do not have to be unique. And, the alternate key used by the dataflow contains unique data.
What is wrong?
Thanks.
