LinkedIn
Twitter
I'm hoping I just have something set wrong, but if not, I believe I found a bug when saving a form.
I have a multipage form (using Show fields for the different pages). With required fields on all the pages. For the "Show field" I use for page 2 I have the Show if validate that a certain field is not blank (so the user can't advance without completing the question).
Because of that "show field" for page 2 is false when the field is not completed, the form defaults to show the "Cancel" and "Save" buttons. This makes sense for cases where maybe you want to allow saving a partial form based on validation, but this is weird the weird part comes in.
If I click save, it correctly says you are missing a required field,
If I make my selection to satiate the requirement, the save button persists and allows me to actually save the data, despite the second page now being available, and having required fields on the second page.
If I navigate to the next page by clicking the tab on top, instead of clicking save it takes me to the next page and then requires the correct fields on that page.
If I do not click save before making my selection, and first make the required selection, then the "save" button changes to "next" as expected.
I understand the value of being able to protect future required fields behind a show validation for complex form triaging, but it seems to be a bug that the "save" button persists just because I tried to click it already and ignores the now required fields on the newly available page.
Is it a bug, or what am I missing?
Note: I understand that removing the Showif() on the Page Header (show field) for page 2 of the form will resolve this in the sense that the user will only ever see the "next" button until the last page. However, I expected the form to honor all required fields once they are shown, which is why I'm not sure if there's a logic reason for this or if it's a bug.
