Error submitting after Field Maps 25.2.0 update

[tbearb]

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.

[tbearb]

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.

[DavidForbuss1]

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.

[tbearb]

@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.

[DavidForbuss1]

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.

[DavidForbuss1]

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.

[ColinLawrence]

@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?

[tbearb]

@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")

[DavidForbuss1]

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")

[ChrisBerryman]

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.