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.
Required fields prevent user from submitting fromAsked by jbellamy on July 08, 2015 at 04:49 PM
Sorry to keep adding to the conditions function which seem to get a lot of forum time, but I am having trouble with a form in which I want the parent to be able to submit feedback for either one, two , or three kids. If they only need to submit comments from one child they should be able to get to the end on page five and hit submit. but instead they get an error message because the fields within page three and four (which are for the other two kids if needed) arent being filled out. I tried going back to see what I used for previous forms but couldn't figure out what I'm doing wrong.
I am having the same problem on my form. It used to be that if the field was not shown on the form due to conditional logic that field would not be required. Now it is requiring the field (Housing Preference) even if the condition to show the field (Division = HS or Institutes) is not true.
Chief Technology Officer
Problem has been solved,
I don't know what you did to correct it but a big Thank You! (if you can tell me that would be even greater so I won't make the mistake next time). I have to say, of all the systems that I use on a daily basis JotForm in my book has to be given top kudos for support. I have yet to see another vendor that responds and perform solutions in the way that you guys do in terms of support.
Apologies for this inconvenience.
It was a back-end problem so there's nothing to be changed on your end. This rises after a certain update but it has been immediately noticed and resolved. Thanks for reporting it by the way.