[BUDI-7465] Conditional UI validation restoring field value

[jmtudela]

Checklist

• [X] I have searched budibase discussions and github issues to check if my issue already exists

Hosting

• Self
  • Method: docker compose
  • Budibase Version: 2.9.38
  • App Version: 2.9.38

Describe the bug If conditional UI is used to make a validation of a field A based on the value of a field B, when you empty field A and then change value of field B the value of the field A is restored.

To Reproduce See attached gif and app export.

Expected behavior Field A should remain empty.

Screenshots

App Export app_example.gz

Desktop (please complete the following information):

• OS: Windows 10
• Browser Brave
• Version v1.57.62 Chromium 116.0.5845.180

_{From SyncLinear.com | BUDI-7465}

[shogunpurple]

This is happening because the value in the first field is invalid and therefore we do not save it (the empty state). We cannot save error states like this or we would be saving invalid states. If you were to change the first field to something valid, this wouldn't happen.

Could you explain a little bit more about what you are trying to do here and we may be able to suggest a solution or workaround?

[jmtudela]

I'm not saving anything when the Field A is restored, and even if I would force a validation (not a save) the value should not be restored. In any case, if you do it the other way, clear Field A and choose Option 2, which is a valid combination, Field A value gets restored.

[aptkingston]

We mean could you explain a little more about your use case, so we could try to give you an alternative solution. The only reason this is happening is because you have configured the validation so that field A is required, and you're setting it to an invalid state in your example here, then moving on and changing field B which causes your conditions to run, and in turn causes field A to remount because you changed something about it.

If you set field A to any valid value, then you'll notice that this behaviour of resetting the field to it's previous value doesn't happen.

As explained, it because conditionals are remounting the field when apply new validation rules, which causes the field to re-render itself, pulling it's value from form state again. This will be the last valid value, which is not the invalid empty state.

Your options are:

• Allow field A to be empty, if you want to allow this
• Accept that invalid values will be discarded when you change something about a field using conditions
• Add an "on change" action to field B to reset field A to some other value when it is changed. e.g. you could just clear field A every time field B is changed
• Use 2 fields, with different validation rules, and use conditions so that only one of them is shown at a time, based on the value of field B

[jmtudela]

Sorry, but I don't get the point. The idea is to require Field A only if Option 1 is selected on Field B. I attach two more examples to be more clear.

Example 1: example1.gz In this example you can clear Field A, modify another field (required message appears but don't reset Field A), and then change Field B what resets Field A.

Example 2: example2.gz In this example Field A must be empty if Field B = Option 1, this does not resets Field A. If conditionals are remounting the field when apply new validation rules, why in this example doesn't do it?