ExB edit widget and related records not saving

[ChrisH2]

Seeking some assistance.

I have set up a 1 to many relationship between a polygon layer and an "Action" table and are utilising smart forms in the new Web Map to allow users to add new polygons and related actions in the table.

The layers are hosted in ArcGIS Enterprise 11.2 and have been published through Pro. Geometry and table editing is enabled. This web map is also added to a  very simple ExB project, but the behaviour (and error) I'm describing below is the same

My workflow is a follows:

- In the Web Map (or ExB), select the polygon layer and open the edit tool

- digitize a new polygon, complete the field attribution and save this record

- Select the polygon again, which reopens the smart form and now there's the option to add a related record

- The edit form for the related record opens fine, the parent GUID is carried over and I can edit attributes

- When I select "create" , the button flashes but nothing happens and the record is not committed. There's no way to move on form this step other than backing out and discarding the edit

I can add related records in Pro after this data is published so I'm thinking that the data structure and relationships are sound. I don't have any of these fields set to mandatory. 

[AlixVezina]

Are you also observing an issue? If you are, please feel free to share as many details as possible, which would be helpful.

[QuantitativeFuturist]

@AlixVezina I have replied to this several times but my message keeps getting removed. I have the exact same issue as @ClangDevGuy 

[ClangDevGuy]

Hey @AlixVezina, I have another thread that goes into a little more detailed about the issue here: https://community.esri.com/t5/arcgis-experience-builder-questions/arcgis-experience-builder-1-12-dat...

It looked like a work around was deployed in the version of ExB 1.13 but this means the ArcGIS Portal version of 1.12  in Enterprise 11.2 won't work. 

[AlixVezina]

Providing an update on our findings regarding the original issue described.

The development team has discovered the source of the problem. Ultimately, it is because the standalone related table is configured to have contingent values, but it does not actually have any display fields or continent values within it. The API "thinks" it should have it in there since the metadata says it does, but in reality they're empty.

This can happen if field groups are defined but no contingent values are defined before publishing the feature service.

For this reason, an error occurs and the related records cannot be created. The team is planning to resolve this issue for an upcoming update and the changes will become available in 11.3.

To fix this issue in 11.2, we would recommend to try republishing the feature service without the field groups or contingent values. If you were planning to use contingent values, perhaps try configuring them again and republishing.

[ClangDevGuy]

Thanks Alix, I will look into field groups/contingent values to see if it fixes the issue. For us, the ExB version 1.13 is working but we just need to host it ourselves outside of the portal for now.