topic Re: Error submitting after Field Maps 25.2.0 update in ArcGIS Field Maps Questions

Error submitting after Field Maps 25.2.0 update

tbearb — Thu, 02 Oct 2025 18:57:16 GMT

Is anyone else experiencing an issue where you get an "ArcGIS.ArcGISError error 1" when you try to submit an edit on a feature that has a related item? This was not an issue in past field maps versions and just started happening when the field maps app was updated.

We are currently running ArcGIS Enterprise version 10.9.1.

Re: Error submitting after Field Maps 25.2.0 update

tbearb — Thu, 02 Oct 2025 18:56:08 GMT

Also, there seems to be something going on when trying to add a related record. See screenshot of when I attempt to add a "Work History" related record by clicking the "Related" button at the top of the pop-up. The option is not there and I must scroll to the bottom to find that creating a related work history record is even an option.

Re: Error submitting after Field Maps 25.2.0 update

DavidForbuss1 — Thu, 02 Oct 2025 19:29:03 GMT

Yep, we're getting the same error. The weird thing is that the records are actually submitting and the attribute rules seem to be populating, but it's not visible on the map until we close it and reload it, then it appears. It's upon submission of a related table entry, and it's the same code that you're getting: ArcGIS.ArcGISError 1

UN version 7, 11.5 -- was working fine until today with the update.

Re: Error submitting after Field Maps 25.2.0 update

DavidForbuss1 — Thu, 02 Oct 2025 19:39:07 GMT

Just tried on my phone which hasn't updated to the new version and it submitted and worked fine. It's definitely the new Field Maps version causing the issue.

Re: Error submitting after Field Maps 25.2.0 update

tbearb — Thu, 02 Oct 2025 20:33:40 GMT

@DavidForbuss1 Yes, we see the same thing where the edit still commits and the attribute rules still fire - provided the user backs out of the edit and agrees to proceed with discarding edits. I have a support ticket in place now.

Re: Error submitting after Field Maps 25.2.0 update

DavidForbuss1 — Thu, 02 Oct 2025 20:47:47 GMT

Good idea, I submitted a ticket too. I got the field crews all lined out on how to make it work, but I hope this gets fixed soon because I can see it getting really messy with extra/unintended records being submitted.

Re: Error submitting after Field Maps 25.2.0 update

ColinLawrence — Thu, 02 Oct 2025 22:00:16 GMT

@tbearb Are you getting this error when submitting the parent feature? Based on your next comment it would seem that you cannot even add a new record to the child table, is that correct? Can you also provide additional info around the relationship type and keyfield? Are there any additional errors you see in the Troubleshooting logs or from the Layers tool?

Re: Error submitting after Field Maps 25.2.0 update

tbearb — Fri, 03 Oct 2025 12:48:24 GMT

@ColinLawrence I've received the error both while conducting a simple attribute edit on the parent feature (water meter point layer) and while trying to submit a child record in the related work history table. A record is technically added to the child table after the user agrees to discard their edits on the related table. The edit still commits, a new table record is created, and any attribute rules that are supposed to fire are fired. The relationship type between the water meter layer and the work history table is simple, the cardinality is one to many, and the keyfields are: GlobalID (origin primary key) and Related_Asset (origin foreign key).

All of this was working the day before the Field Maps app was updated and has been working for the past 4+ years.

Looking at the logs, I noticed when we were getting the error message in Field Maps, the timestamps correlated to this error in the logs: [EDITING] stopEditing failed with error: ArcGISError(code: 1019, description: "SQLite constraint violation.", details: "SQLite: 19\nAbort due to constraint violation")

Re: Error submitting after Field Maps 25.2.0 update

DavidForbuss1 — Fri, 03 Oct 2025 14:21:30 GMT

We have a similar setup:

Getting the same error: 10/3/25, 7:12:41 AM [EDITING] stopEditing failed with error: ArcGISError(code: 1019, description: "SQLite constraint violation.", details: "SQLite: 19\nAbort due to constraint violation")

Re: Error submitting after Field Maps 25.2.0 update

ChrisBerryman — Fri, 03 Oct 2025 17:59:49 GMT

Has a bug been logged for this?

We see an error when submitted feature edits, but our error contains the text "restricted pathway" according to my users. The edits still goes through but it makes it seem like nothing happened. These features also have related tables as well but they are not editable via field maps.

Re: Error submitting after Field Maps 25.2.0 update

tbearb — Fri, 03 Oct 2025 18:07:13 GMT

To my knowledge no bug has been logged yet. I have an open case with support but they're still going through troubleshooting / investigative phases. I was told, however, that more tickets are now being logged against this issue.

Re: Error submitting after Field Maps 25.2.0 update

DavidForbuss1 — Fri, 03 Oct 2025 18:11:08 GMT

I ended up submitting a tech support ticket like tbearb did, and I have an ESRI rep helping me out. Do you have attribute rules running on the layer that's throwing the errors? And is it a Utility Network layer? I have a non UN layer that has no attribute rules and lives on a separate Enterprise GDB (running on the same SQL server as my UN GDB) that I was able to submit related records for with no errors.

Re: Error submitting after Field Maps 25.2.0 update

DavidForbuss1 — Mon, 06 Oct 2025 14:18:10 GMT

I worked with ESRI tech support, and they discovered that having any duplicate layers in the map would cause the error. They have a bug created now:

We have created a bug: BUG-000179924 - Attempting to edit a feature with related records in a web map that contains duplicate Utility Network layers throws "Unable to Submit 'The operation couldn't be completed.(ArcGIS.ArcGISError error 1.)'" error in ArcGIS Field Maps version 25.2.0, which you will be able to view and track in My Esri. Please see this document for the details on how to keep track of the request: https://support.esri.com/en-us/bug-enhancement-request-status

Re: Error submitting after Field Maps 25.2.0 update

JeffShaner — Mon, 06 Oct 2025 14:51:41 GMT

Thank you for posting this and for contacting Esri support. We hope to resolve this issue soon.

Re: Error submitting after Field Maps 25.2.0 update

tbearb — Mon, 06 Oct 2025 15:42:17 GMT

Thanks for the update! That makes more sense now. I was on a call with support and we created two new web maps. One web map was a complete duplication of the existing web map that was showing the editing error and the other web map was a brand new one that had only the troublesome layer within it. The new web map that had only a single layer in it did not show the editing error but the web map that was a duplication of the existing map (which has layers that are duplicated) still produced the same error.

Re: Error submitting after Field Maps 25.2.0 update

JeffShaner — Mon, 06 Oct 2025 22:02:18 GMT

@DavidForbuss1 were you adding duplicate layers in your map to work around the lack of support for editing Subtype Group Layers in Field Maps? If so, perhaps you might want to consider changing the composition of your map?

BTW, up next with UN in Field Maps is support for Subtype Group Tables (both viewing in the pop-up and editing in the form). We are planning to add this support in time for the next network management release (ArcGIS Enterprise 12.1).

Re: Error submitting after Field Maps 25.2.0 update

SanneMikkelsen — Tue, 07 Oct 2025 08:16:07 GMT

Same problem here. ArcGIS Enterprise version 11.4. Have problems in several maps in Field Maps 25.2.0. No problems when we use the older version of Field Maps. We have problems both in editing webmaps and in maps without editing functions (layers not available).

Re: Error submitting after Field Maps 25.2.0 update

DavidForbuss1 — Wed, 08 Oct 2025 14:34:09 GMT

I believe we had the map set up that way because it was carried over from the LGIM schema. We also had a SQL script running to create a view, which highlighted the lines with related records. If a line didn’t have a related record, it wouldn’t appear—so we had to add the parent layer underneath to ensure everything was visible. We now have an attribute rule to push the most recent related record date onto the parent layer so we can just symbolize off of that (since we no longer can do direct SQL views on UN).

Re: Error submitting after Field Maps 25.2.0 update

ColinLawrence — Wed, 08 Oct 2025 17:48:03 GMT

@SanneMikkelsen what are the layer errors you are seeing in the maps without editing? Do you mind creating a separate post for this with some details?

Re: Error submitting after Field Maps 25.2.0 update

GregHeintz1 — Thu, 09 Oct 2025 20:06:47 GMT

We were getting the same error with one of our work order request maps in Field Maps (it was a non-UN layer). The work around, until the Bug is fixed, is to publish a second feature service and use AGO Assistant to replace the URL of the feature service that is duplicated. Once I did this, I created and submitted a feature worked without the error.