Question

You are building a nightly integration that pushes product records from an external ERP into Dataverse using UpsertRequest with an alternate key defined on the 'productcode' column (a string field). During testing, some upserts fail with an error indicating the record could not be resolved, while others succeed. Investigation shows the failing ERP records contain product codes with leading or trailing spaces that do not exactly match the values stored in Dataverse. What is the most appropriate way to make the upsert reliably match existing records?

Accepted Answer

Trim and normalize the productcode values in the integration code before building the alternate-key EntityReference used by UpsertRequest

Answer

Switch from UpsertRequest to a RetrieveMultiple query followed by conditional Create or Update requests

Answer

Add a second alternate key on the primary GUID field so the upsert can fall back to it when the string key fails

Answer

Disable duplicate detection rules on the product table so the mismatched values are accepted