How about using a conditional region around the input instead of using Hide… that way it will not be sent to the server when blank, so then you can use your default 1 logic.
It would be more appropriate to use dynamic required/disabled attributes, instead of using a conditional region for fewer fields. dmx-bind:required="somecondition==1"
Thanks @mebeingken. Well my preference would be to use as is which is using show. Only because there are other fields that are also shown or hidden which have certain validation rules depending on the number entered in the input in question. Subsequently if I were to try the conditional region. How would I do that exactly?
Conditional regions require additional DIV surrounding the input. And just for one field, it does not make sense to me.
We use a mix of both approaches depending on the form.
If there are multiple fields we need to disable, we use CR. If there are a couple, we use hide & disabled dynamic bidnings.
Thanks @sid I think this is probably what I need. So i’ve added a ‘disabled dynamic attribute’ with a condition that uses the value of the radio group above it. (see screen shot ) … which seems to work.
Just to add reference to what @mebeingken suggested on this regarding using conditional regions. and in fact what @sid mentioned that in certain situations he uses both show/hide and CRs. I have discovered that using both methods combined was the solution for this particular section of the form.
So thank you both!