Multi level dependent fields

Migrated from legacy feedback forum with 169 votes.

 

I'd like to have more than 1 level in the dependent fields in forms.

HubSpot updates
Multi level dependent fieldsHubSpot Product Team
Feb 17, 2020

I'm afraid I'm not 100% sure, @Andreas, it's been a little while since I worked on the Forms products. Tagging in @DomRychlik who's PM on Forms. Dom should be able to confirm for you Smiley Happy

Multi level dependent fieldsHubSpot Product Team
Jun 20, 2019

Afraid not @joshtaylor, I'm no longer part of the team working on the Forms product but tagging in @DomRychlik who may be able to confirm for you.

62 Replies
New Contributor

 Me too!!

Occasional Contributor

We really need this feature!

 

Currently we use embedded Cognito Forms which is far from ideal. 

New Contributor

Would make forms shorter and tidy if when a contact select the preferred communication just shows the fields required instead of having all the fields and had to make them optional instead. Other systems allow it is time to Hubspot upgrade their game

Regular Contributor
 
It would be nice to have the ability to add a dependent field in a form to another dependent field. Therefore the third question in a form is not dependent on the first question; it is dependent on the second (which in itself is a dependent field)
 
For example, we'd like to be able to qualify our customers in this format:
1. Ask:  Do you run a business?
          A. Answers Yes - ask "In what industry?"
                     aa. Answers Transportation - ask "What is your fleet size?"
                                   aaa. Answers 1-5 trucks - leave message "Sorry, weare not able to help at this time."
                                   bbb. Answers 50-100 trucks - give them an option to fill out more information (name and phone number) to get started
          B. Answers No - leave the message "Sorry, we only only work with business owners at this time."

Occasional Contributor

Apart from having multilevel depedent fields, it would be great to have the option to make them optional/ required as well as hidden in case you want to use them for internal purposes. For example, in my form I am asking for the country and based on that a state selection shows. For internal use it would be extremely helpful to be able to create another hidden dependent field which will match the state with a "reporting zone". I could use a workflow workaround for this, but it's unconvient.

Also, unlike in my specific case where I need the extra dependency for internal purposes, there are many scenarios when multilevel dependent fields are needed on the customer side as well as on the company side in order to better fit both needs. 

Occasional Contributor

It would indeed be really helpful to have this feature!

Occasional Contributor

Really need this as well,

 

We have clients that need to cancel/update/get a quote for orders and I can't use the same form field 'file number in more than one dependency' really frustrating. 

Occasional Contributor | Gold Partner
Occasional Contributor | Gold Partner

Totally agree, it would be useful to add Rich Text box to the field also.  Make it look a little more professional.

New Contributor

we need more than one level of dependent fields for dropdown lists. I have created one level dependent field for dropdown selection but we need the same for multi-level. can you please add this feature asap?

New Contributor

I need this solution in my account. 

New Contributor

yes please, us too! 

New Contributor

Please hubspot add this

Esteemed Contributor

We also need dependent dropdown select properties. Salesforce calls this concept the "Dependent Picklist". Here is our use case: If ValueA is selected for "Industry", then in "Sub-Industry" property, only display the values belong to ValueA (ValueA1, ValueA2, Value A3, etc.)

 

@marthamartinez , @marci-mango 

For those looking for properties to be conditionally displayed or made mandatory, I guess that's another idea and it's here: Conditionally display and/or make mandatory properties

Occasional Contributor

We need to have multiple levels of dependent fields as well as the ability to make them required. Please update us on if or when this could be added.

 

Esteemed Contributor

About a year ago I voted on this, so would like to do so again to bump it up!

 

Just came across this issue again, where we need a dependent field for an already dependent field.

 

It's making some of our customer surveys very ugly! Cat Surprised

Visitor

I'm also looking to build a form with multiple dependencies.

 

Also, would like to be able to use a property differently in each separate dependencies. For example, choose option A and you are required to fill out your First Name but choose option B and you are not required to fill out your name but I want to use the property without a requirement, but I can't even place that property because it's already being used. 

New Contributor

Do we get any response on this from Hubspot on where this functionality is on their roadmap???

I see a lot of users that are interested in it for already more than a year, and so am I.

When is this coming?

New Contributor

This feature would solve many form issues. For example, if someone responds "other" to a dropdown select dependant field, it would be helpful to have another field pop up that allows them to specify what "other" is. 

New Contributor

It would be tremendously helpful for us (and I presume others as well!) if you could add dependent fields TO a dependent field. i.e. A visitor answers question 1. Based on their answer, another field populates. Based on THAT answer, an additional field populates. Our users are very diverse and when we're collecting information from them, it would be helpful if there were a better way to sort of tailor our form to them so we can collect answers for all follow up questions in advance, streamlining post-submission tasks. 

Regular Contributor | Gold Partner
Regular Contributor | Gold Partner

I was looking for this functionality the other day, and this would have saved a huge amount of time and ease of use for clients. The worst part about creating custom functionality to "create" a second level dependency, is that if the customer changes anything eg. values, you have to go back to the custom script and edit it to fix any issues this would cause.

 

It would make things a lot easier from a usability standpoint if this were included.