|
BLOG
|
Overview Starting with ArcGIS Survey123 web app v3.25 (March 2026), the web app now fully supports the 'calculationMode' parameter defined in XLSForms. This update aims to align the web app’s calculation behavior with the field app, providing a consistent experience across the platform and preventing accidental data overwrites when editing existing records. Core change: Shift in default calculation behavior Prior to version 3.25, the web app ignored the calculation mode parameter and effectively treated all calculations as "Always." The new version introduces a significant shift in default behavior: Version Default Description v3.24 and earlier Always Calculations update automatically whenever a referenced field changes, potentially overwriting previously submitted data without warning. v3.25 and later Automated (Auto) (Default) Calculations do not automatically run when editing existing records to protect data integrity. A "Calculate" icon appears if a change is detected, requiring a user click to update the value. Supported calculation modes You can now explicitly control calculation behavior by setting the calculationMode parameter in the bind::esri:parameters column of your XLSForm. The following modes are supported: Always: Calculations are reactive and immediate. The field will automatically update whenever any referenced input changes, regardless of whether you are submitting a new record or editing an existing one. Automated (Auto): This is the default behavior. In Submit mode (new records): It functions like "Always," where calculation expressions are evaluated whenever any of the inputs in the calculation expression change. In Edit mode (existing records): It protects existing data. If a referenced input changes, the field will not overwrite the stored value automatically; instead, a button appears, allowing the user to manually trigger the update. Manual: Calculations are never triggered by input changes. The field remains static until the user explicitly clicks the "Calculate" button to evaluate the expression. WhenEmpty: The calculation logic only triggers if the field is currently null or empty. If the field already contains a value, the calculation is bypassed, preserving the existing data. Solutions: Restoring legacy behavior For users—such as those managing ArcGIS Solutions—who wish to maintain the "Always Calculate" behavior without republishing existing surveys, the following options are available: 1. Updating the XLSForm (Recommended) For new projects or surveys that can be updated, you can preserve the legacy behavior by explicitly setting the mode in the XLSForm: Column: bind::esri:parameters Value: calculationMode=always 2. Using recalculate=all via URL To address the breaking change in v3.25, the recalculate URL parameter has been enhanced to act as a global override. Parameter: &recalculate=all Effect: Appending this to the survey URL forces all questions to use calculationMode=always. Availability: Now supported in both Submit (new records) and Edit modes. Benefit: Restores the v3.24 experience instantly without requiring a survey republish.
... View more
Thursday
|
1
|
0
|
128
|
|
POST
|
Hi @RalphPlummer , thank you for reporting this. We will be deploying a hotfix to address the issue this coming Monday night (PST). Please try again on Tuesday or any time after. We appreciate your patience.
... View more
04-16-2026
01:43 AM
|
1
|
1
|
484
|
|
POST
|
Hi @jvarasanz , Thank you for the additional information. You are correct—you will need to set the calculation mode to always as a workaround. With the introduction of calculation modes in the web app, the default behavior is now auto. We plan to enhance our documentation to better cover these specific scenarios. Thanks again for your feedback.
... View more
04-03-2026
02:11 AM
|
0
|
1
|
692
|
|
POST
|
Hi @EdwinCarrillo , I was able to reproduce the issue. The workaround is to add calculationMode=always to the ${modo_form} field. Background on this change: With the 3.25 release, we introduced support for calculation modes in the web app. The default status (when left blank) is now "auto" mode. In "auto" mode, the calculation triggers for new records; however, when editing an existing record, "auto" will not re-trigger a calculation if a value already exists. Normally, for visible questions, a user could manually trigger a recalculation via a button. Since this question is hidden, that button isn't available, so setting the mode to "always" is necessary to ensure the calculation runs during edits. We will update our documentation to better cover these scenarios. Thanks again for the detailed information you provided!
... View more
04-03-2026
01:33 AM
|
0
|
0
|
471
|
|
POST
|
Hi @EdwinCarrillo , Thanks for providing that information. We deployed a hotfix on March 30th, could you try publishing the survey again with the latest version and let us know if the issue persists?
... View more
04-01-2026
08:51 PM
|
0
|
1
|
506
|
|
POST
|
Thanks for the confirmation! Glad to hear it resolved the issue.
... View more
04-01-2026
08:21 PM
|
0
|
0
|
617
|
|
POST
|
@Theisen we have deployed a hotfix for this issue. Could you please test it again on your end and let us know if it’s resolved?
... View more
03-31-2026
10:47 PM
|
0
|
1
|
983
|
|
POST
|
Awesome, thanks for the update! Glad to see it's working.
... View more
03-31-2026
10:46 PM
|
0
|
0
|
983
|
|
POST
|
Thank you for confirming the fix for the web form publishing issue. Regarding the inputMask issue, my colleague Ruth will follow up with you in the other post.
... View more
03-31-2026
10:44 PM
|
0
|
0
|
986
|
|
POST
|
Thanks for confirming! Great to hear it's all sorted.
... View more
03-31-2026
08:26 PM
|
0
|
0
|
795
|
|
POST
|
Hi @Derrick_Westoby , we have deployed a hotfix for this issue. Could you please test it again on your end and let us know if it’s resolved?
... View more
03-31-2026
12:08 AM
|
0
|
1
|
882
|
|
POST
|
Hi @GabrielaReyes , we have deployed a hotfix for this issue. Could you please test it again on your end and let us know if it’s resolved?
... View more
03-31-2026
12:02 AM
|
0
|
2
|
1274
|
|
POST
|
Hi @SMH-Rio ,thank you for being a long-time user and for your honest feedback. We deployed a hotfix tonight that may address this. Could you please try again to see if the issue is resolved?
... View more
03-31-2026
12:01 AM
|
1
|
0
|
1274
|
|
POST
|
Hi @SIGISCIAMSA , we deployed a hotfix tonight that may address this. It is difficult to confirm from the screenshot if your specific case matches the fix, so could you please try again to see if the issue is resolved?
... View more
03-30-2026
11:58 PM
|
0
|
0
|
1274
|
|
POST
|
Hi @jeffhyderBRVA , we have deployed a hotfix for this issue. Could you please test it again on your end and let us know if it’s resolved?
... View more
03-30-2026
11:56 PM
|
1
|
1
|
1275
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Thursday | |
| 1 | 04-16-2026 01:43 AM | |
| 1 | 03-31-2026 12:01 AM | |
| 1 | 03-30-2026 08:34 PM | |
| 1 | 03-30-2026 11:56 PM |