JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
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.
Require/Unrequire conditions are setting fields to required even if conditions with higher priority set them to non requiredAsked by omacworld on April 22, 2016 at 09:56 AM
I recently built a form (https://www.jotform.com//?formID=51787746115968) that was working when I tested it last week, but as of at least the day before yesterday, conditionals have quit working properly.
The form is to register for a martial arts tournament. We have different board breaking events and different sized boards (based on age of competitor). If someone signs up for a breaking event, they must buy boards of some type. My logic goes like this:
if any of "creative breaking", "distance breaking", "power breaking - fist", "power breaking - elbow" are selected, then show (and require) "boards - child or speed", "boards - juniors", "boards - adults". if any of "boards*" are chosen, unrequire "boards*".
Like I said above, this worked when I created and tested the form. However, when a competitor tried to sign up yesterday, the unrequire didn't work, and they were required to buy boards of all sizes. I've tried to change the logic to include a 0 choice and make the unrequire be based on "board*" not equal to 0, but that doesn't work either.
For now, I'm going to have to disable the requirement of purchasing boards, but that means we could have people showing up to the event without having purchased the boards they need to compete.
I took a look at your form and I can see what you mean. It seems that when you set the conditions, no matter how they are set, the fields are left as required, until you uncheck the field and then check it again, when it updates the same properly.
As such I will raise this to our developers to check it out further.
As soon as they have any update they will let you know about the same through this thread.