I'm using applyEdits to update attributes of existing Features on a FeatureServer using globalIDs. e.g.
useGlobalIds=true&updates=...&rollbackOnFailure=false
However, when testing this I found that if I supply a GlobalID that does not exist I still get a success response, e.g. (the second globalId does not exist):
"updateResults": [
{
"objectId": -1,
"globalId": "{B3AB1BA9-A4DE-46E6-92C8-4E34A421726A}",
"success": true
},
{
"objectId": -1,
"globalId": "{55555555-A4DE-46E6-92C8-4E34A421726A}",
"success": true
},
If I try the same thing with our internal ArcGIS portal implementation I get an error:
"updateResults": [
{
"success": true,
"globalId": "{B3AB1BA9-A4DE-46E6-92C8-4E34A421726A}",
"objectId": 1
},
{
"success": false,
"globalId": "{55555555-A4DE-46E6-92C8-4E34A421726A}",
"error": {
"code": 10512,
"description": "Update for the object was not attempted. Object may not exist."
},
"objectId": null
},
Note that for successful updates the Portal server also returns the existing objectId, whereas ArcGIS Online is always returning -1.
Is this a known limitation with ArcGIS Online?
