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; } } }

Webforms Not Running Calculations

jvarasanz_nifc

Starting this morning, our web forms are no longer running calculations, which is breaking the workflow for webhooks that rely on these calculated attribute values.

We tested the same form in the Field app, and everything works as expected there.

Please advise.

Find more posts tagged with

Accepted answers

All comments

jvarasanz_nifc

Just in case, I went back to the xlxs form and added calculationMode=always to all calculations and it seems to be working, although everything has been working fine for over 4 years now.

Derrick_Westoby

I started having issues this morning with report generation. Not the same issue as you, but a separate issue that also has been working fine for years on forms.

JodyZhengLiu

Hi @jvarasanz ,
Thanks for reporting this. We rolled out version 3.25 yesterday, and it’s possible this update is related to the issue you're seeing. To help us investigate, would you be able to share your XLSForm file so we can try to reproduce the behavior? You can send it directly to me at zliu@esri.com.

Thanks,
Jody

IDEMuniMendoza

Same for us! Furthermore, forms have lost the link between relationship classes in repeats

IDEMuniMendoza

Perhaps this will help you... @ZacharySutherby suggested I set calculationMode=always in the bind::esri:parameters column, and so far it has worked for my web forms that were having problems.

jvarasanz_nifc

Good morning Jody,

Please accept my apologies for the delayed response.

The form experiencing issues retrieves existing records, so I don’t believe providing the XLSX file would be helpful in this case.

That said, there is a field in the form designed to update the previously calculated status of a record based on changes made to other fields that were not previously populated. Because of this, the calculation should run automatically. However, I understand this may not occur if those fields were already populated and that, in that situation, the best approach would be to set the calculation mode to “always.”

Please let me know if you need any additional information.

JodyZhengLiu

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.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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