You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users sometimes put a calculate on a visible field in an attempt to have a dynamic default. That calculate is evaluated on form finalization, replacing any user-provided value. If the calculate evaluates to blank, the form successfully finalizes even if the field is required.
If a calculate clears a required value, the form should fail validation. This doesn't do a lot to help users identify their misuse of calculates because more often than not a calculate will produce a value. I'm still filing the issue because it points to something not quite right about the order things are evaluated in on finalization.
The text was updated successfully, but these errors were encountered:
Software versions
all
Problem description
Users sometimes put a
calculate
on a visible field in an attempt to have a dynamic default. Thatcalculate
is evaluated on form finalization, replacing any user-provided value. If thecalculate
evaluates to blank, the form successfully finalizes even if the field is required.Steps to reproduce the problem
See getodk/collect#4566
Expected behavior
If a calculate clears a required value, the form should fail validation. This doesn't do a lot to help users identify their misuse of
calculate
s because more often than not acalculate
will produce a value. I'm still filing the issue because it points to something not quite right about the order things are evaluated in on finalization.The text was updated successfully, but these errors were encountered: