Is this also related to https://forums.wildapricot.com/forums/308932-wishlist/suggestions/8827282-condition-based-display-of-fields-for-multi-level ?

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.

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."

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.

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.

This is similar to other wishlist items regarding logic/rules/conditions so we can make smarter forms. WA's forms are currently all-or-nothing, so members have to scroll past things that don't pertain to them, e.g. "Child #6 Name", "Child #6 Age", "Child #6 Tshirt size".

Examples of desired functionality include:

"# of children in family?" -> "6" = opens 6 fields for names, ages, sizes.

"Are you 65 or older?" -> "yes" = applies senior discount

"Are you already a stockholder? -> "no" = opens stock purchasing options with extra charges attached
OR -> "yes" = opens field to enter stock number

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.

Issue:

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.

For Example:

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"

I support having conditioned fields upon type of answer or choice of related prior field or fields.

Definitely. For us it would be most useful in event registration forms....., but I expect it would be great to make membership forms a bit more clever!

Good idea, thanks for sharing. Is anyone else interested in this kind of enhancement?

I would appreciate comments from other users who need this - and additional examples.

I would like to have a "subfield" option for my membership fields. With that, a member who chooses a certain option of the field is given additional multiple choices. For example, a member who picks "music" can then pick from "piano", "guitar", "singing" and such. Sub-fields would help with a more logical organization of member profiles.