We have a survey that had defaulted a fields values to 0. This is used for summing the fields later on. Initially if the value was not zero, the user would select the field, highlighting the zero and replace it with the new value.
After the most recent update:
1) when the user selects a field containing the defaulted zero, the zero is not replaced after the user enters a new value. Before when the field was selected, the zero would be highlighted and the zero would be replaced with the new values the user typed in.
2) If the user does not delete the zero and proceeds by entering a new value it is placed after the zero (a leading zero; ex. 05). They are then promoted with an invalid notification but are still able to submit the data. When they do this and submit the data with a leading zero in the field the value they entered is not recorded and the data is lost.
I have attempted to negate this by adding a regex, which would force them to remove the leading zero, but S123 does not seem to recognize the expression. regrex(., '^([0-9]|[1-9]\d*)$')
Thanks
Solved! Go to Solution.
Hi Kyle,
Can I ask that you check the Early Adopter Community? It sounds like there is some improvements for 3.7 that might at least partially address what you are seeing (validation with a leading 0).
Hi Kyle,
Can I ask that you check the Early Adopter Community? It sounds like there is some improvements for 3.7 that might at least partially address what you are seeing (validation with a leading 0).
Thanks James