Simple Hide/Show Dependency Not Working

  • Profile Image
    Asked on September 03, 2011 at 07:22 AM


    My experience of Jotform has always been a positive one except when it came to bugs and anomalies with the hide/show function. For some reason this mainstay of form development seems to constantly conjure up anomalies.

    I haven't used Jotform for a while due to requiring the use of an edit autoresponder mode that drives emails on updating data - a very useful function. But i think I have cracked a workflow with your edit link function ...

    However, hit on a problem straight away with hide/show dependencies still not doing what they are supposed to ...

    Please see the following form:

    Bottom Line: Hide Show doesn't work with Hidden Field set to a value and used in the conditions area

    Would it be possible to get this going or I'm going to have to go straight back to another form builder


    Regards Mark

  • Profile Image
    Answered on September 03, 2011 at 03:38 PM

    Ok, well hopefully that hasn't been ignored and is being worked upon. In keeping with the problem is another dependency problem ... import this form from the url ...

    check the conditions and see if you can see what's wrong - the plan field shouldn't be showing. The difference is that we are using radio button field to hide the plan field. That radio button field is also hidden with a condition. If you remove the condition so that it is showing the behaviour works to hide the Plan field.

    Bottom Line - Hide/Show Dependencies do not work with hidden fields forcing the condition. They have to be showing.

    Unfortunately critical for what I would like to do...

    Regards Mark


  • Profile Image
    Answered on September 04, 2011 at 04:00 AM

    Hello Mark,

    Hide/Show conditions will not trigger with a prepopulated hidden box or other fields for that matter. It wil not trigger using URL prepopulation either.

    In other words, hide/show conditions will only trigger on user-initiated actions, i.e., typing in a text box or selecting options in drop downs, radio buttons and check boxes.

    I will confirm with our developers if they have any plans of changing that rule to include triggering of hide/show conditions via prepopulation/setting default values. We will let you know of any updates. Thanks!


  • Profile Image
    Answered on September 04, 2011 at 04:26 AM

    I guess I spoke too soon. After further testing, here's what I gathered:

    Setting a default value to a field can now trigger conditions. URL prepopulation still can't. Hidden boxes cannot trigger conditions in any way.

    The conditions in the form do not work because they are dependent on a "hidden box" field, which we know cannot trigger a condition.

    The second form,, is not working because it is dependent on another conditionally hidden field.

    A workaround I suggest is to replace hidden boxes with css-hidden text boxes. Click here to view a thread related to your issue in which I have included examples.