Survey123 Connect Update 3.25 - inputMask submission error

[GabrielaReyes]

Hi all,

I have a couple of surveys created in Survey123 Connect that had been functioning prior to the most recent Survey123 Connect update (3.25.27). Since the update, I have been getting errors on the web versions when trying to submit a record. After troubleshooting, I found the cause of the error was from hidden fields with inputMasks (ex. 9999; >XXXX9999).

Error: "Survey contains errors: 3. Press here to navigate to each error." When you press to navigate, there are no errors it takes you to.

Workaround solution: Remove inputMask parameter from the hidden fields and republish

I'm wondering if this is an additional bug from the most recent update? These inputMasks were functioning prior. 

[EdwinCarrillo]

Solution: downgrade 😕

[Ruth_JiatengXu]

Hi @GabrielaReyes ,

Thanks for sharing here! The hidden inputMasks should not prevent form submission, we will include a fix in the upcoming Hotfix2 planned for next week.

However, this does not appear to be a regression introduced in the March release. Have there been any other change to your form? The input "9999" does not satify the input mask ">XXXX9999", so it should have prevented submission in eailer version as well.

Thanks,

Ruth

[GabrielaReyes]

Hi @Ruth_JiatengXu ,

Has the Hotfix2 been rolled out? There have been no other changes to the form. The example '9999' was one of the inputMask, not an input example!

[Ruth_JiatengXu · Accepted solution]

Hi @GabrielaReyes ,

Sorry for the confusion, I understand the issue now. It is caused by the new calculation mode feature.

Please update the calculation mode to "always" for the question that has an input mask set.

• If you are using Connect, put "calculationMode=always" in "bind::esri:parameters".
• If you are using the web designer, please follow the screenshot below.

The calculation mode controls when calculations are performed in questions and is set to "automatic" by default. When the source question changes, this mode can prevent recalculation in the target question, which means your hidden question cannot receive the updated value.

Thanks,

Ruth

[GabrielaReyes]

This resolved the issue, thank you!