Error updating addresses via REST ConstituentService

This is a stale data error that typically happens when you GET the object, subsequently attempt a PUT, but with something else having changed that same record in between the time you did the GET and PUT.  Are you trying to use the xml from the GET multiple times?  The normal pattern is GET, change data, PUT, then if another change is needed do another GET first.

Ron

From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Michael Gelman
Sent: Wednesday, March 21, 2012 3:59 PM
To: Ron Wilson
Subject: [Tessitura Next Generation Forum] Error updating addresses via REST ConstituentService

Hey folks:

We are investigating the REST services, and we're getting an error we're having trouble figuring out. 

<ErrorMessages xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><Errors><ErrorMessage><Code i:nil="true"/><Description>Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [Tessitura.ConstituentService.Domain.AddressEntity#4839768]</Description><ErrorPath i:nil="true"/></ErrorMessage></Errors></ErrorMessages>

The situation is that we took the output from a GET call to get the address record, made a minor change the to XML, and fed it back into the service with a PUT.  That's when we get the error.

Any advice?  Anyone get this to work?

--Michael

(Apologies if this is in the wrong place -- I didn't see any discussion of the REST APIs in the "regular" technical forums.  I'm happy to repost over there if that's a better place.)

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

This is a stale data error that typically happens when you GET the object, subsequently attempt a PUT, but with something else having changed that same record in between the time you did the GET and PUT.  Are you trying to use the xml from the GET multiple times?  The normal pattern is GET, change data, PUT, then if another change is needed do another GET first.

Ron

From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Michael Gelman
Sent: Wednesday, March 21, 2012 3:59 PM
To: Ron Wilson
Subject: [Tessitura Next Generation Forum] Error updating addresses via REST ConstituentService

Hey folks:

We are investigating the REST services, and we're getting an error we're having trouble figuring out. 

<ErrorMessages xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><Errors><ErrorMessage><Code i:nil="true"/><Description>Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [Tessitura.ConstituentService.Domain.AddressEntity#4839768]</Description><ErrorPath i:nil="true"/></ErrorMessage></Errors></ErrorMessages>

The situation is that we took the output from a GET call to get the address record, made a minor change the to XML, and fed it back into the service with a PUT.  That's when we get the error.

Any advice?  Anyone get this to work?

--Michael

(Apologies if this is in the wrong place -- I didn't see any discussion of the REST APIs in the "regular" technical forums.  I'm happy to repost over there if that's a better place.)

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!