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]

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.

[DavidForbuss1]

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.

[DavidForbuss1]

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 

[JeffShaner]

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

[tbearb]

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.

[JeffShaner]

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

[DavidForbuss1]

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

[GregHeintz1]

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.

[SanneMikkelsen]

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

[ColinLawrence]

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