I am completely stumped. I was pleased to be able to update attribute data for a data set stored in ArcGIS Online using the Field Map App while being onsite. However, it appears that not all the data is treated the same. Using the same app to edit the same data set that was originally created at the same time, I am able to edit one data point but not able to edit a second data point using the same keystrokes. When I press the Update button, the feedback I get is “Unable to Submit.” Does anyone have an idea of what might be causing this?
Solved! Go to Solution.
As it turned out, the data set limited the types of data that particular field would accept to due to an old range domain assigned to it. I had renamed an old field to try to save time. The end result was that it cost me a lot more time because the numbers I was trying to enter were outside the range.
If you are having a similar problem, I recommend you check for subtypes and domains.
The problem was determined quite some time ago. I apologize for not posting at that time.
Hi Paul, is there additional info to the error like "geodatabase not found"?
Unfortunately, no. The lack of information makes it especially hard to troubleshoot.
I’m curious about the geodatabase not found that you mentioned. I have experienced that and things start to get hairy after it occurs. Do you know what it actually means?
did you ever figure this out? I have the same issue, "Unable to Submit. Unable to complete operation. Internal error during object insert."
I did not. It is the season to use that same workflow soon. I will let you know if I learn anything new.
In my case, the error was caused when users using Field Maps enter a value that contradicts the layer filter on the map. For example, if the layer is filtered to only show features with Status = Active, but users update it to Status = Inactive using Field Maps, the error appears. Depending on what you want shown on the map, you can probably just symbolize the layer such that changing of the values via FieldMaps does not "violate" the layer filter, potentially circumventing the error.
As it turned out, the data set limited the types of data that particular field would accept to due to an old range domain assigned to it. I had renamed an old field to try to save time. The end result was that it cost me a lot more time because the numbers I was trying to enter were outside the range.
If you are having a similar problem, I recommend you check for subtypes and domains.
The problem was determined quite some time ago. I apologize for not posting at that time.