You can just send back the lock_version you got with the get. No need to bump
it - that happens on a successful update. The response to the update will
include the new lock_version, like this:
{
"status": "Updated",
"id": 2,
"lock_version": 23,
"stale": NULL,
"uri":
Huebschen, Alan M wrote on 2020-04-17 14:26:24:
> I've been attempting to update existing resource records through the API, the
> records already exist and I'm trying to upload modified versions of the JSON
> but I'm getting an error in response.
>
> 'error': 'The record you tried to update has
pace_Users_Group] Error updating resource records through API
Hi all,
I’ve been attempting to update existing resource records through the API, the
records already exist and I’m trying to upload modified versions of the JSON
but I’m getting an error in response.
'error': 'The record you tried to
Are you modifying the lock version?
Donald R. Mennerich, digital archivist
New York University Libraries
don.menner...@nyu.edu (212) 992-6264
On Fri, Apr 17, 2020 at 10:26 AM Huebschen, Alan M wrote:
> Hi all,
>
>
>
> I’ve been attempting to update existing resource records through the API,
Hi all,
I've been attempting to update existing resource records through the API, the
records already exist and I'm trying to upload modified versions of the JSON
but I'm getting an error in response.
'error': 'The record you tried to update has been modified since you fetched
it.'
At first
