Feature Service no longer editable in map viewer after making changes to map viewer form

[LJackson29]

Hi -

I have a map created in map viewer that contains an editable Feature Service (as well as a number of other layers. I have used the forms feature to create a form that I pull into Experience Builder.  I was updating the settings in the form, and all of a sudden I am no longer able to edit the feature service in the map. I had made no other changes to the map. Editing is still enabled for the layer in the map, and it is still editable if I pull it into a different map. This is the second time this has happened to me (after a substantial amount of time configuring pop-ups, the form and experience builder) with this feature service. After the first time, we created a completely new service and I started with a fresh map, and now it has happened to me again. Does anyone have any suggestions? 

Many thanks,

Leila

[RussRoberts]

Can you share the map and layer to the group with russell_jsapi invited to it and we can see if there is a property blocking the editing.

[LJackson29]

@RussRobertsThanks for your response - I unfortunately cannot make it public.

[RussRoberts]

Would recommend opening a support ticket and they can possibly look into it.

[LJackson29 · Accepted solution]

I submitted a ticket for this, and it is a bug that is currently under review.

Suggested Work around: Ungroup the required fields which have the conditional expression applied.

BUG-000148876- Layers configured with a form in Map Viewer cannot be edited if the form contains a group, required questions, and conditional visibility, and the conditional visibility expression is not triggered.

[RussRoberts]

I think that issue you posted has been resolved. The conditional visibility is working in the sample map listed.  

[LJackson29]

@RussRoberts I am not sure what the sample map is that you are referring to, but I have encountered this issue 3 times in the past 2 months, most recently last week. ESRI did further testing this week and concluded it was associated with this bug that is still under review.