Field won't accept edits for one feature - works for all others

[DavidPike]

Hi,

I have a hosted feature layer which has been published from Survey123.  One field from this feature layer is later used to add reviewer comments to a survey submission e.g.' Approved', 'Need more info', 'missing paperwork' etc.

This editing is done in Experience builder.  However when a this field is edited for this particular feature/entry we get the message 'Something went wrong - Edits could not be saved: Error'.

The next step was trying to do the same edit in the Data tab of the hosted feature layer (no special formatting, characters etc., just inserting 'TEST' and various other simple strings).  In this instance, on entering the text and clicking out of the text box or pressing enter, the display just refreshed and then showed nothing entered.

There are no domains, and other rows for the same field can be edited fine.

has anyone got any ideas as this is slightly confusing.  Any comments or suggestions at all are much appreciated.

Thanks

[ChristopherCounsell · Accepted solution]

If you open the browser console and look at the network traffic it should give you a response to the request (e.g. updateResults or applyEdit) with an error code and description.

Taking a wild stab in the dark at potential issues:

• Something to do with the foreign key constraints and globalids - check your relationships and globalids or guids specific to this record and related
• Invalid text entry (previous discussion on this for users with '<NULL>' inserted as a string into a text field, instead of actual Null

If you share the error code or give more info (survey form and workflows) we may be able to narrow it down further.

[ChristopherCounsell]

https://community.esri.com/t5/arcgis-online-questions/correct-invalid-geometry-for-hosted-feature-la...

I guess it could also be the feature being out of bounds? This related?

[DavidPike]

Thanks, the dev window had a helpful response from ApplyEdits that a field had invalid HTML (<someone@somewhere.com>).  The post here https://community.esri.com/t5/arcgis-data-interoperability-blog/writing-html-and-other-amp-lt-and-am... explains why.  removing the tags then solved the issue.

Thanks for the steer.  Also other issue is the same layer but unrelated as have solved that now.