Required fields do not work with radio buttons, when submitting form, it continues to ask for a field that is filled in (radio button) and will not submit the form.
Any suggestions?
Required fields do not work with radio buttons, when submitting form, it continues to ask for a field that is filled in (radio button) and will not submit the form.
Any suggestions?
Can you show us a screenshot of the radio button? does it have two options or only 1? I have never run into difficulties with a radio button unless it only has 1 option and is required. Then it will need to be selected. In those cases, I would recommend using a Checkbox and it's more logical to use for a single option statement/question.
EDIT: Is the radio button controlling a required field from being hidden or visible using the field rules? If so, maybe it is causing a problem that you are misinterpreting. Check here for a possible solution: https://answers.laserfiche.com/questions/61503/Forms--Add-Rule-so-that-a-field-is-required-when-shown
Hey Curtis,
I've seen this happen before, but I'm not quite sure why it happens. If you have a required radio button field, at times, even if you have an option selected, it will tell you to "Choose an option before you can submit your form" or something along those lines.
Generally, you should be able to delete and recreate that field to fix the issue. If you have attempted this and you're still finding the issue, please include a screenshot of the field's configuration that is causing trouble and we'll take another look.
I would like to think that deleting the fields in the form, and recreating them is the answer, however it is not, and the fields are random. Besides, I'm talking nearly 100 fields, not just 1 or 2. The workflow that goes with this is doing some major work, and changing this would be devastating, for the workflow took over 6 weeks to build and perfect.
If you're finding this error on ~100 fields, we might be dealing with a larger issue here. I'd suggest having your VAR open up a support case so they can take a deeper look. Thanks for your patience as we work through this.
any resolution to this? Is this a new bug?