My app has a Decimal input with 2 decimal digits and 0.5 step in one of it's forms. It has a "Valid if" constraint if the input value is greater than a certain value it will throw the given error message. Until a few days ago if u increased the value by clicking on the "+" button the error message was shown if it passed the maximum set value. Now it doesn't. The error is shown only if u try and save the form.
This is the constraint formula: [_THIS] < [MAX VALUE]. "THIS" being the current input value and "MAX VALUE" is a column where the value is calculated.
Any idea what happened?
Thanks.
Solved! Go to Solution.
The release was deployed yesterday and it should now work without the save.
1. You can try to check [_THIS] if change it to [Column Name].
2. You can check type of values in current column and in [MAX VALUE]. May be need to use DECIMAL() function.
3. If the Appsheet now behaves as you wrote, then make the value input not in the form, but in the detailed view with editable columns. In this case, the error will be processed immediately after the value is changed.
It sounds this is the same issue we found out last week where the validation process was changed. Earlier all validations were figured out when you went away from that field, but now you need to save first to see it. The fix should be coming for this.
Mind-boggling that this bug made it past a developer, let alone into the field.
I haven't updated the application for more than half a year. This is the second time an appsheet update breaks a functionality. First time it broke the app. Users couldn't sync because of that. Something was done to List() function. I had to wrote the expression in another way without List().
Waiting for validation on out of focus to be reinstated then.
The release was deployed yesterday and it should now work without the save.
My users confirmed yesterday that it's working as it should.
Thank you!
User | Count |
---|---|
16 | |
10 | |
8 | |
5 | |
5 |