June 2026 Update - Hidden fields no longer calculating in ExB

[JeremyBrown4]

I'm seeing a new issue since the latest update. When trying to create or edit features in ExB using the edit widget, hidden fields are no longer calculating. These are not fields with conditional visibility, just hidden fields with simple calculated expressions. I don't see this issue coming from field maps forms using the same layer and visibility/calculation setting, so I'm guessing this is an ExB bug. Anyone else noticing this?

[WillyG]

Hi @JeremyBrown4 I noticed an issue yesterday with an intersect expression and that intersect relied on the conditional visibility expression used a field to choose which area to perform the intersect if overlapping multiple areas. It now no longer calculates unless that field has a value.  I had it working perfectly pre update so that it would calculate even if this field wasn't showing. Not a hidden field as such but it could be related to what you are seeing? 

[JeremyBrown4]

Thanks for the response WillyG! I don't think my issue is the same one you're having though. I have no conditional visibility, or any other calculations that rely on or reference the field in question. The "calculation" on this field is simply adding text, about as basic as it gets. If I hide the field the form will submit with no data in it, even though it's a required field. If I mark the field as visible it will run the calculation successfully. I know I can accomplish what I'm trying to do by adding a default value to the template, but I have many other ExBs with complicated calculations being run on hidden fields.

[Trenn]

Hi @JeremyBrown4 I've noticed several fields that have calculated expressions or default values are not populating when feature created through the Edit Widget in Experience Builder. These same fields continue to populate correctly using Field Maps. Additionally, when creating a new feature or editing an existing feature using the Edit Widget, text fields are only accepting one character at a time. After entering a character, I have to click back into the field in the Edit Widget to add another character. These fields continue to populate correctly when using Field Maps. Lastly, the Edit Widget is not honoring custom configuration to display specific fields within the widget. These are all new issues for me since the June 2026 update.

[StephanieW]

Hi @JeremyBrown4 I encourage you to log a Support case if possible so we can take a closer look at the app and configuration. https://support.esri.com/en-us/overview

[OliviaK_99]

I am also having this issue, specific to the Experience Builder edit widget.

[OliviaK_99]

I tried to make the hidden calculated fields required and this seemed to fix the issue for me...

However I am experiencing slow performance with the edit forms. It looks like the form has to refresh every character.

[ErinCourtney]

I also tried making the fields required, and it did not work for me. Did you do anything else, and what are your editing settings on the widget? Add records/update records, and what about the editing settings on the layer?

[OliviaK_99]

Never mind spoke too soon, making it required didn't work. Making the fields visible is the only thing that has worked for me so far. My widget is set to interact with the map widget. I get the same result trying to edit in the web map itself. The fields in question that were hidden are now set to not editable, required, and visible to get the calculation to run. The layer allows adding and updating attributes and geometry.

[CraigGillgrass]

@OliviaK_99 see my reply here:
https://community.esri.com/t5/arcgis-online-questions/june-2026-update-calculated-expressions-break-...

We have a fix for the form refreshing on every character.