Question

You are building an integration client that uses the Dataverse Web API to update account records. Multiple background services may update the same account simultaneously. The business requires that an update must fail if the record was changed by another process after your client last retrieved it, so that stale data is never silently overwritten. Which approach should you implement in your PATCH request?

Accepted Answer

Include an If-Match header set to the ETag value (RowVersion) that was returned when the record was retrieved.

Answer

Include an If-None-Match header set to "*" so the request only succeeds when the record does not yet exist.

Answer

Add a Prefer: return=representation header so the updated record is returned and compared client-side.

Answer

Set the MSCRM.SuppressDuplicateDetection header to false so Dataverse rejects conflicting writes.