I have a form which has a conditional section in it where some fields are hidden based on the selection of a radio button
All fields on the form are required and have client side validation set accordingly
Unfortunately the hidden fields are validated so validation fails as the hidden fields are empty
I am trying really hard to be able to say the entire project is 100% wappler, no customisation
Before i resort to changing things in code view, is there an official wappler way of disabling validation when field is hidden?
No, sadly they are being validated even when disabled
I have removed the “hide” condition and added a “disabled” condition . I can see they are disabled but they still try to validate
@George , I tried making fields disabled and read only and also tried manually adding
dmx-bind:required=“a_condition_here”
So the resultant code is as follows When "active" <input type="text" class="form-control form-control-sm dmxValidator-invalid" id="id_GuarantorName" name="GuarantorName" aria-describedby="input2_help7" placeholder="Enter Guarantor Name" is="dmx-input" value="" required="">
When de-activated the required="" is correctly removed <input type="text" class="form-control form-control-sm dmxValidator-invalid" id="id_GuarantorName" name="GuarantorName" aria-describedby="input2_help7" placeholder="Enter Guarantor Name" is="dmx-input" value="" readonly="" disabled="">
So the required="" option is being toggled but validation still occurs
Am a toggling a wrong value?
Well I did also a research on the HTML5 standards for input validation (with our validator we just extend the standard HTML5 validation) , but couldn’t anything except novalidation that switches off the whole form validation.
Maybe @patrick can advise and if it’s not possible currently maybe we can add new functionality in the validator to auto skip hidden (invisible) fields
Can get around it temporarily i think by adding some dummy content to the fields with an onclick() event of the controling field but stopping validation of hidden fields would be great.
I just remembered - why don’t you put a conditional region around it (dmx-if)
when condition is not met - its whole contents is removed from html dom - so no validation will go there!
I had a similar situation in my project, but it was non-critical form. So I just removed all validations.
I wanted to validate form inputs not only on the page, but also in the server action’s post/get variable properties.
I haven’t tried dmx-if, but any suggestions for server action?
OK, huge apologies, i must quality from the fool of the month.
Disabling the fields does work, I forgot that when importing fields into a server action, the validations were also imported. The the data was being rejected at server action level, not client. I removed server action level validation for those fields and disabled the fields at client end and all seems fine now
You can leave the Client Side validation in place for those fields, simply remove validation from the Server Side. We do the same for some forms based on select list values. This way the fields are validated if they are shown and ignored if they are not.
