What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
Changing option text in a radio button control breaks conditionsAsked by DragonsVolleyball on January 20, 2017 at 09:54 PM
I have a radio button control with a number of options, and had set some conditions where I checked if the user had selected a particular button. I have found that if I change the text of the option, this breaks the condition.
While this is not entirely unexpected, I have found that there is no easy way of knowing that the condition is broken. I have only worked it out by editing the condition to find that the space where I would select the radio option was blank. There is no indication of a problem when looking through the list of conditions.
Could this be rectified please, as it is extremely time consuming to require re-testing of a complex form for such apparently minor changes?
As I can only assume that everything works now and we are glad you were able to figure it out, we would like to apologize for any inconvenience this had caused you.
Although there is only an indicator in the condition wizard if the fields involved are deleted, field names/labels that are changed will also be changed in conditions automatically. However, parts of the fields like "options" are not manually changed especially when typed inside an Update/Calculate conditional logic.
What I usually do if there are cases where I have to edit any part of a field is to check if there are any associated condition(s) with that field first. You can easily do that by clicking the "condition icon" found at the top-right-corner of the field when selected in the builder page.
Or by opening the condition wizard and selecting the fields
Thanks Mike_G, your advice on preventing the issue in the future is appreciated. This of course only helps if you are aware of the potential of this problem to occur. I think it would substantially reduce 'why is it not working' frustration of users if this were addressed in some way.
Thanks for your response, DragonsVolleyball.
It is indeed very helpful if a person gets to be aware that his condition will not work due to conflicts through means of an alert or a notification on the side, similar to when a field gets deleted. I find this to be a good idea so I escalated a feature request to the development team. Unfortunately, I cannot guarantee that this can get implemented soon. But in any case, once this is added, we'll let you know.