Is anyone running into this aside us?
Error is as follows -
Solved! Go to Solution.
Hi folks,
Turns out this is now a bug. BUG-00015717.
No word on when it will be resolved, but figured there is someone out there with a similar issue. 🙂
I would open up your browser's Network tab and watch what kind of POST it's making to the service when you try to edit. Maybe make an edit in the classic viewer and compare the two?
All good thoughts here. Yes, that was done and the calls are different. What's odd is that the viewer is doing something dissimilar to classic or Field Maps.
A difference from classic I'd expect, but Field Maps, that's interesting... What about one of the Instant Apps built on top of the new viewer? Some of them include editing tools.
Is it only this layer, or do you see it with other registered services? Are there null values in integer fields? I have no end of headaches with the way certain (but not all) parts of the Esri-verse handle null integers.
Good morning Josh,
I was able to dig into this further, examining the payloads going up, etc....
The difference between the classic viewer, Portal (10.9.1) viewer, and ArcGIS Online's viewer is that the new viewer is adding "returnServiceEditsOption=originalAndCurrentFeatures" to the string that pushes the edits.
For ArcMap published services....no issue. For ArcGIS Pro published services, its an automatic fail w/ the code...
"error":"code":500,"extendedCode":-2147467259,"message":"Unable to complete operation.","details":["Error: Combination of parameters rollbackOnFailure = false & returnServiceEditsOption = originalAndCurrentFeatures for applyEdits operation is not supported."]
The classic viewer does not have it, nor Portal, so I am assuming it was the recent updates to the viewer which causing the issues.
WRT using Instant Apps, I have not tried that route yet, but passed it over to the analyst who is experiencing the issue. For the time being, they are working around the issue using Field Maps. I offered to pull this into Portal for them, but there is some hesitancy there for the moment.
Fun stuff. Hope no one else is experiencing this issue.
Hi folks,
Turns out this is now a bug. BUG-00015717.
No word on when it will be resolved, but figured there is someone out there with a similar issue. 🙂