I'm using applyEdits to update attributes of existing Features on a FeatureServer using globalIDs. e.g.
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):
If I try the same thing with our internal ArcGIS portal implementation I get an error:
I have the same problem. Updates: [
{
"attributes": {
"globalId": " {EBFB9BDF-3CC2-4D20-80F1-E9953BEE47C5}",
"ddpcr_copies": 0.73,
"lim_max_p": 1.01,
"lim_min_p": 0.50,
"gotas_tot": 51671,
"gotas_pos": 32,
"gotas_neg": 51639
}
}
]
{ "attachments": { "addResults": [], "updateResults": [], "deleteResults": [] }, "addResults": [], "updateResults": [{ "success": false, "globalId": null, "error": { "code": 10528, "description": "Input feature does not have a global id." }, "objectId": null }], "deleteResults": [] }
I think this might be a different problem. You may want to double check the exact name of the GlobalId field for that layer as I have seen before that it can be case-sensitive.
FYI, Esri have logged a bug for the issue I experienced:
"We were able to reproduce the issue in trial and developer subscription accounts. As this issue is reproduceable over different subscription a defect was created to address this issue. The defect number BUG-000159592 can be used to track the progress of and even escalate the defect in My Esri."