Experience Builder Edit Widget Problems After June 2026 Update
Hoping someone is able to help – ever since the June 2026 update, we have been experiencing all sorts of issues with our Experience Builder Edit Widget.
My team has made no changes to the Experience in over a month prior to the June 2026 update, so I am assuming these errors are a result of something that went wrong with the release.
We have a Survey123 survey that is linked to this Experience Edit Widget (hosted feature layer). Making edits in Survey123 seems to work fine right now. But any time we try to make edits to the feature through the Edit Widget we get the errors below like the form logic isn’t firing correctly.
These issues also occur in the Web Map. We are attached to a bug right now (BUG-000185911) regarding this, but it is still ‘In Review’ and this is causing our organization a lot of heartache right now. So wondering if anyone has found any workarounds yet…
Error 1: “Value should be one of the listed values”
When I click on the drop down, it tells me:
If I blank out the selection, it clears the error:
Error 2: “The selected feature has hidden fields with invalid values”
The funny thing about this one is that these fields are hidden because they are not relevant (based on previous responses). These fields SHOULD NOT show up on this feature at all, so it doesn’t make sense why we’re getting this error for the hidden fields.
Error 3: “Value should be one of the listed values”
This question is a multiple select in Survey123. I know there are limitations with the Edit widget and multiple-select questions right now, but we’ve never had this issue come up purely from previously entered data from Survey123. It’s like when the response is viewed in the layer now, it just cannot accept the previously entered data.
Error 4 (oddity – not actually throwing errors):
Notes field now shows “0/2147483647” (characters) while blank. We haven’t changed the character limit for the field for years and it is typically 5000. Not sure why this is suddenly showing up like this.
Error 5: Unable to delete photo attachments (when prior to the June update this worked just fine)
I suspect this is linked to the above errors. We’re unable to save changes to features (including deleting attachments) because we can’t clear the errors for hidden fields.
@sosero - additional info for Bug 000185911
Thank you
My customers just told me that they have been experiencing errors 1 and 3 since the update. On error 3, even when there is no value at all, it is saying that "no value" is unsupported or it will show it as completely blank and say, "value should be one of the listed values". I was able to duplicate the issues. We have historic values that are no longer in the domain value list that need to remain as they are. Because it is essentially making these changes required, we are unable to continue updating data as needed from Experience Builder. Field Maps is not having these same issues.
Additionally, not mentioned above. The app is significantly slower and has glitches like pictured below. Widgets will just be completely blank. The only way to fix it is to clear browsing data and log back in. Feels like all I have been doing is fielding complaints about performance and glitches this month.
