Condition-based display of fields for multi-level questions
I would like to request creating a way to display a registration field based on a previous field selection.
For example, If I have the question "Are you interested in learning about this committee?" If the answer is yes, I would like a second question to display. If the answer is no, I do not want the second question to display.
I've been told this is not a current feature in Wild Apricot but think this would be very useful for membership, registration and donation forms.
Yes, This is a feature that would make our membership application better
John Koehler commented
Also agree. This would be a very important feature and would help considerably with the membership form functionality and ease of use. At the very least it should be able to do conditional based membership fields that only display based on a previous field selection.
Jordan Dempster commented
I totally agree. Conditional display and branching logic would be invaluable for our registrations. Would make a big difference to the usability of the forms.
I agree with the others: this is pretty necessary functionality to have in 2018!
In my situation within the pages presented by the registration widget I need to be able to conditionally display a required custom contact field based on the type of event. I all need to conditionally display a content widget at the front of that flow based on the type of event.
LDP Connect commented
Would very much like to see this with events. Very important to us.
Treva Stose commented
This is our most important feature request. It would also be most helpful if there were more design flexibility for forms. At the very least, we would like to place first names, MI and last names on the same line. WA's vertical forms get very long and daunting and do not encourage members to complete the forms.
Tonya Suits commented
Not having conditional responses is a serious negative mark for our needs. I am going to need to reconsider using Wild Apricot for the other orgs we manage if this is not a feature implemented soon. It is a requirement for the events we manage and produce. Period.
Based on the date of this thread that it was originally shared FIVE YEARS AGO, it looks like it isn't something that is going to happen. :(
LeBon Abercrombie commented
I have also asked for conditional branching in Polling questions
Alex Sirota commented
Yes it absolutely is related! Thanks.
AdminEvgeny Zaritovskiy (VP Technology of Wild Apricot by Personify, Wild Apricot by Personify) commented
Alex Sirota commented
Not just membership fields. This should be available on event custom fields. For example if you use an extra charge radio button it would be nice to present an optional or required set of fields, based on the radio button selected for extra charge present more fields.
This is useful when collecting extra information on registrations without using the guest feature which is much more complex and cumbersome to use.
The basic idea of membership fields is a good idea, but this is useful only on a registration of a new membership or renewal. Sometimes you want to record some extra information DURING a membership period rather than on initiation or renewal, this is where events can be used effectively with conditional logic on radio buttons and checkboxes and drop downs.
Becky Jenn commented
I would love to see logic/branching ability with membership fields so that members only see the fields that they need to complete that apply to them. For example: "# of children in family = 1" they get the name, birthdate, and tshirt size options fields shown for 1 child. If "# of children in family = 6", logic can be set up to show those same sets of fields for 6 different children. Then the family with 1 child doesn't have to scroll through 5 more empty fields of children's information options before they get to the next thing they need to complete.
It's a basic submenu logic. PLEASE please implement it as soon as possible.
If someone selects in the menu or from a drop down option they want to eat meat, for example, then, there should be a sublogic for people to select whether they want their meat rare, medium rare, medium, medium well or well done! If someone selects they want chicken instead of meat, they don't need additional level of choices. Thank you for implementing this! Would be very very helpful.
I agree that this is needed. Our previous provider had this feature and it almost made me stay with them. Conditional based on a previous field is sufficient, but conditional fields based on Registration Types would be used by us as well. I agree this is a "must have."
Doug Armstrong commented
This would be great! For example, we do a dinner and we ask folks how many guests they will have. Based on the number of guests=X, I would like to present X menus for them to preselect meals. Perhaps we are doing an event and there are X guests per registrant and each get a shirt, need to be able to as X time what size shirt we need. This is a must have.
Mike Felton commented
I agree that Wufoo is a great example of how to do conditional form construction. It would make membership joining forms shorter by being more intelligent.
Becky Jenn commented
YES YES YES!!! I've been begging for this for years. Our member signup forms need to be smarter. For us, we could have a third of our current membership levels if only we could make the signup forms smarter. Our forms could also look about 1/3 shorter, but members have to scroll past fields that don't pertain to them, but are necessary for some members (e.g. Child #6 Name, Child #6 TShirt Size, Child #6 Medical Conditions...). Wufoo.com has great rules/logic/conditions that can be added to forms that are just one way to do it.
Ability to have fields interact and have rules between fields. For example, if you change field X, it automatically adjusts field Y, or you can't enter data in field Y unless you have data in field X.
Certain fields are tied in to a 'parent' field. Need to be able to create a function in which only certain fields will be an option for the member to choose if they have chosen a parent field.
If parent field value is "A", second field value can only be "a,c,e"
If parent field value is "B, second field value can only be "b,f"
and so on and so forth.
Currently, this is how it is showing:
if parent field value is "A", second field value can be "a,b,c,d,e,f"