nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Encuentra más publicaciones etiquetadas con

ArcGIS Online

Accepted answers

cgillgrass

@LauraWaddle_-_FS we have a fix for this going out tonight.

All comments

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.

ErinCourtney

Seems I have it working with making the fields visible, but we'll have to work on some other work arounds because some of these fields can be edited by internal users, but not the public.

bbollin

hello! @JeremyBrown4 , @ErinCourtney, @OliviaK_99, @Trenn We have tried to reproduce this with hidden calculations and default values in the form, but are unable to see the behavior you are describing. If you have a working repro case, please DM me with access to the data or a copy of the dataset and the steps to reproduce the issue. Thanks!

HeatherGonzago

Would it be possible to provide a repro map showing the issue you describe above? We are having a hard time reproducing this but it could be we're missing a key step/part of the form's configuration.

cgillgrass

@OliviaK_99 see my reply here:
https://community.esri.com/t5/arcgis-online-questions/june-2026-update-calculated-expressions-break-with/m-p/1711274/highlight/true#M69069

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

ErinCourtney

I just sent you a link to our ExB, Webmap and HFL. Please let me know if you need anything else from me to do the testing.

LauraWaddle_-_FS

@JeremyBrown4 I noticed the exact same thing! I had to make the fields visible in the editing form for them to calculate, which is not desired because now the users see several fields in the Edit widget that are not meaningful to them.

@ErinCourtney, @OliviaK_99, @Trenn @HeatherGonzago @bbollin @CraigGillgrass @Jianxia

For the ESRI folks that have responded, I have a public-facing map that you can test with: https://maps.arcgis.com/home/item.html?id=578afb037fe141129d3c9845bca89970 (the 'BURN_MONTH', BURN_YEAR', 'END_DATE_TXT' and 'ANONYMOUS_USER' fields for the Partner and Private Burn Points layer are set to visible, but I would like for them to be hidden. When hidden, the calculations don't run). The map is included within an Experience Builder app: https://maps.arcgis.com/home/item.html?id=94d5022f4cb647f68ca77bcb733082bd (the Edit widget is under the accordion item named Step 2).

Thank you!

bbollin

Thanks @LauraWaddle_-_FS, the team is actively investigating this

cgillgrass

@LauraWaddle_-_FS we have a fix for this going out tonight.

LauraWaddle_-_FS

🎉Thank you!

LauraWaddle_-_FS

My editing form is working like it did before the June AGOL update. Thank you for deploying the fix last night!

JeremyBrown4

I just tried making the hidden field required and it seems to be working for me. I'm going to leave the field visible for now though. I am also seeing extremely slow performance in the edit widget, even after the form refresh patch.

JeremyBrown4

I can confirm that hidden field calculations are working for me too, albeit a little slow, but it sounds like that's due to another issue. Thanks for the update @CraigGillgrass, and to the ESRI team for getting this resolved!

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.