ArcGIS Online - Error: edits could not be saved

[Kantoor__DataCount_-_Verkeerso]

Hello everyone,

I'm having the following error while editing data that's been uploaded recently: Oops, something went wrong, Edits could not be saved error. 

The features are editable cause these settings were on:

It doesn't help to load the data in a new map. Weird enough it is possible to edit the data while loading in Map Viewer Classic without having this error. So it seems to be a Map Viewer problem. Is somebody else issueing the same problem?

Regards, Marius

[ABishop]

Hello,

At first glance I would say to check off the "Add" and "Delete" and possibly the "Update" check boxes?

[Kantoor__DataCount_-_Verkeerso]

Thanks Amanda, for your reply!

We tried your suggestion, but that doesn't fix the problem. When all boxes are unchecked, the edit modus in the Map Viewer turns off as it should. When the boxes are checked again, the same errors appears when we try to save edits. Therefore, it seems like it's not related to the kind of edit options.

As said before the problem only appears in the new Map Viewer, in the old viewer it is possible to edit the data.

Kind regards, Frank

[ABishop]

When you initially published this service did you make sure the feature edit options were checked?  

[Kantoor__DataCount_-_Verkeerso]

Yes, we did, but that didn't fix our problem.

However, we did find the solution: a textfield had '<Null> written as text, instead of a real Null-value. By recalculating the values to a real Null, we managed to save our edits.

Thanks for your help!

Kind regards, Frank

[BrookeAumann]

Thank you for this! I was having a similar problem and this was the issue.

[JeremyLw]

An older thread, but I discovered a similar issue with the new Map Viewer giving an error while editing attributes "Edits could not be saved. Unable to complete operation error". Related to the issue described earlier with <Null> characters typed into a text field (see https://support.esri.com/en-us/knowledge-base/error-something-went-wrong-edits-could-not-be-saved-00... for full description) - I discovered if you have any "< >" in your text fields, it throws this error. Maybe it interprets it as wonky HTML tags and throws a fit.  The fix is to delete those characters in Pro or ArcMap. Single "<" or ">" characters don't seem to be a problem, just the closed "delimeters".