A .NET service updates Dataverse account rows through the Web API.…

Question

A .NET service updates Dataverse account rows through the Web API. To avoid overwriting other people's edits, it retrieves each row, stores the @odata.etag value, and later sends a PATCH with an If-Match header carrying that value. Some PATCH requests now fail with HTTP 412 Precondition Failed. What does the 412 response indicate, and how should the service respond?

Accepted Answer

The row changed after it was read, so the service should retrieve the current row and ETag, reapply its change, and retry — Think of the ETag as a timestamp on the version you read. When you send If-Match and get 412, Dataverse is telling you somebody else saved the row after you looked at it, so your copy is stale. Don't blindly resend it; re-read, reapply your change, and try again.

Answer

The service hit a service protection limit, so it should wait for the Retry-After interval and resend the identical PATCH

Answer

The If-Match header is unsupported on PATCH, so the service should move the ETag into an If-None-Match header instead

Answer

The calling user lacks Write privilege on the row, so an administrator must add the account Write privilege to its role

Short Explanation

Full Explanation