Question

You are building a nightly integration that imports product records from an external ERP system into Dataverse. Each ERP product is uniquely identified by the combination of a warehouse code and a SKU number, neither of which alone is unique in Dataverse. The integration must create new products or update existing ones without generating duplicates, and it never has the Dataverse primary key (GUID). What must you configure to make UpsertRequest work correctly in this scenario?

Accepted Answer

Define a single alternate key on the entity that includes both the warehouse code and SKU columns, then reference the record using that key in the UpsertRequest target.

Answer

Define two separate single-column alternate keys, one for the warehouse code and one for the SKU, and pass both keys in the UpsertRequest target.

Answer

Enable change tracking on the entity so Dataverse can match incoming records to existing ones during the upsert.

Answer

Populate the primary key GUID on each incoming record before calling UpsertRequest so Dataverse can locate the matching record.