Expand my Community achievements bar.

Display logic within custom field choices

Avatar

Level 9

10/9/17

In addition to the display logic that already exists for custom forms, we have a need for field choices to show based on the response to a previous question.

For example:

Question 1: Product Family
Choices 1: Home Services, Customer Service, Web App, etc..

If I choose 'Home Services in question 1 I only want to display limited choices for question 2

Question 2: Product
Choices 2: Home Services Product 1, Home Services Product 2, etc....

I need the Product list to be a comprehensive list of all products for reporting purposes, but want to have display logic within the question to only show certain choices based on an answer to a previous question.

14 Comments

Avatar

Level 2

11/9/21

Hi Dev team, are there any calendly options that are better for customers in the Pacific Time Zone? We would love to participate.

Avatar

Level 2

11/9/21

Hi Dev team, are there any calendly options that are better for customers in the Pacific Time Zone? We would love to participate.

Avatar

Employee

11/15/21

Hey everyone,


I apologize for the time zone inconvenience. We definitely don't want you to sacrifice the sleep time :)


Please feel free to schedule Pacific Time Zone-friendly time slots via this link.


We look forward to talking to you.

Avatar

Level 3

5/26/23

This is still a major need for our Workfront use. Will this functionality be included in the new form designer?

 

Our use case is similar to others - if a user selects an option in one field, we want to hide or filter-out certain options in other fields. It would be similar to how Typeahead filters work, but more dynamic (which was also requested in this post here). If display logic was used at the field option level, that would work for us.

 

A bonus would be if the field maintained that behavior across all forms that it was used on. I can see this being tricky to implement given that different forms may not have the same combination of the same fields, but luckily Adobe is super smart and could probably figure that out.