Troubleshoot "Unable to Submit" in Field Maps App

[Paul_E]

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?    

[RodellZorilla]

Hi Paul, is there additional info to the error like "geodatabase not found"?

[Paul_E]

Unfortunately, no. The lack of information makes it especially hard to troubleshoot.

[LanceKirby2]

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?

[PamelaLocke1]

did you ever figure this out?  I have the same issue, "Unable to Submit.  Unable to complete operation.  Internal error during object insert."

[Paul_E]

I did not. It is the season to use that same workflow soon. I will let you know if I learn anything new. 

[RodellZorilla]

@Paul_E @PamelaLocke1 

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.

[Paul_E · Accepted 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. 

[YvonneMorales · Accepted solution]

As of May 2025, I ran into the same issue but was able to fix this by deleting the fields in my layer that do not allow null values and recreated them. I then updated the form in field maps designer to be required there, instead. I also renamed the field the same as the old field to automatically update the form.

[tikola]

You are in the hard core of 2025 variant of this issue. Some attribute field does not allow NULL value and same field does not have a default value. Then you end up very easily to this error message. Is it in generally error - not really I think? It is just message you get when you define schema in certain way and try to add feature against that schema.

In my case there was a long list of attributes and few last ones were mandatory ones and I just missed those on that long list. So in my perspective it is not really error but more like case where software works just as designed. Only error is that GUI where the work is done is not just suitable for that task.