API/Projection call issue with leads - Lead already modified again

Hi ​@bdoucette,

First you need to get (using a GET) the existing record,  and add the value ‘@odata.etag’ as   ‘If-Match’ property to the request header.

 

After getting the @odata.etag from the GET, you must remove the backslashs that served to represent double quotes in the JSON object.

if your @odata.etag is the one in the example above, for instance. Before adding as the if-match to the header the highlighted backslashes needs to be removed.

“W/\"Vy8iQUFBU2dDQUFpQUFCQU12QUFCOjIwMjUwMTI4MjExMzI3Ig==\” 

\ backslashes needs to be removed
 

Then add the value as if-match to the request header.
in this case: if-match  “W/"Vy8iQUFBU2dDQUFpQUFCQU12QUFCOjIwMjUwMTI4MjExMzI3Ig==” 

Thank you & Kind regards,
\ Krishantha

Hi ​@KrishanthaRutterKey 

Thank you for getting back to me so soon, I appreciate it.

How could I get the eTag from a record if the entire REST call is only one call. The transaction to create the person record and the account contact record occurs after IFS receives the projection to create the lead, but before it actually completes it. When you submit the projection call, IFS grabs the contact information, creates the person/contact, then updates the lead with the newly created account contact. We don’t control any of that.

Again, thank you,
Bryan

Have you added &odata-debug=json to your request to see if you can get some clues to confirm your suspicion? I’ve found that that often includes lots of detail about the full internal process.