I updated to the latest version, and the relevant fields in edit mode stopped working in the XLSForm.
Hi @EdwinCarrillo , thanks for reporting this. Would you mind sharing your XLSXForm so we can try to reproduce the issue on our end? Please feel free to email it to zliu@esri.com
Thanks,
Jody Zheng Liu
That's the problem, the group doesn't appear when in edit mode on the web version when used, for example, on a dashboard.
| type | name | label | hint | guidance_hint | appearance | required | required_message | readonly | default | calculation | relevant | ||||||||||||||||||||||||||||
| note | modo_form | modo_form | hidden | pulldata("@property", 'mode') | |||||||||||||||||||||||||||||||||||
| begin group | grp_avaliacao | <b>AVALIAÇÃO DA OBRA:</b> | w1 | ${modo_form} = 'edit' | |||||||||||||||||||||||||||||||||||
| end group |
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?
The problem was identified in version 3.25.27, which was the last update.
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!