Share
Report
10Hi community,
we're using CRM Web API Batch operation to transfer data from an external system A to client's CRM. To make it as fast as possible we send the maximum 100 records in one HttpPost via CRM Web API. All updates were supposed to be updates, no inserts.
After a few moments we discovered that Web API does an upsert by default so that false GUIDs from System A gets created in CRM. Not good. We added header "If-Match: *" and this fixed our problem, only updates to existing records are allowed. All good thus far.
After few more moments we discovered that not all updates from System A were sent to CRM. Debug logging revealed that all those 100 records HttpPost chunks having a single non-existing GUID were discarded. Not good.
I tried to look how to gain a header set where all valid (99pcs 204's) updates would be accepted and only the non-existent records would be failed (1pc 404). https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/webapi/perform-conditional-operations-using-web-api
Anyone know a way out of this?
BR, Timo
Trying avoid this: The other way is to process the answer and remove the offending GUID away from the original send.
All responses (
Answers (
