# Multi level dependent fields

**URL:** <https://community.hubspot.com/t/multi-level-dependent-fields/1558>\
**Category:** HubSpot Ideas\
**Tags:** forms\
**Created:** [April 10, 2017, 12:14pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558 "2017-04-10T12:14:16Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![mchvatal](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mchvatal/32/14279_2.png) [@mchvatal](https://community.hubspot.com/u/mchvatal)\
**Post date:** [July 2, 2020, 6:24pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/81 "2020-07-02T18:24:06Z")

</div>

Chiming in my support for this feature too! We have a use-case where we need the lead to be able to select whether they would like to provide a home address or practice address and then have the appropriate fields appear. NOTE - in this scenario, we store practice information in the contact record and not the company record.

---

<div class="post-metadata">

**Author:** ![jkowalski](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jkowalski/32/53612_2.png) [@jkowalski](https://community.hubspot.com/u/jkowalski)\
**Post date:** [August 14, 2020, 5:20pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/82 "2020-08-14T17:20:31Z")

</div>

I need to add a customer assessment/ needs analysis form. Would like one question at a time, and if they answer one way the questions would stop with a message saying they are not qualified.

---

<div class="post-metadata">

**Author:** ![ErikaJ](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/erikaj/32/2401_2.png) [@ErikaJ](https://community.hubspot.com/u/ErikaJ)\
**Post date:** [August 27, 2020, 10:19pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/83 "2020-08-27T22:19:42Z")

</div>

Commenting to follow this. Would really like to see this feature added.

---

<div class="post-metadata">

**Author:** ![cdavie1](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cdavie1/32/43030_2.png) [@cdavie1](https://community.hubspot.com/u/cdavie1)\
**Post date:** [September 2, 2020, 9:31pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/84 "2020-09-02T21:31:52Z")

</div>

Fantastic to hear it is in review!!

---

<div class="post-metadata">

**Author:** ![esivertsen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/esivertsen/32/62359_2.png) [@esivertsen](https://community.hubspot.com/u/esivertsen)\
**Post date:** [September 3, 2020, 7:30am UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/85 "2020-09-03T07:30:31Z")

</div>

This would be a very handy solution esp. for handling any regional responsibility,

it will allow us to customize subregions (provinces/states/territories) to match local structures.

Not to mention market segments and -verticals…

---

<div class="post-metadata">

**Author:** ![Stevie-Kv](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stevie-kv/32/97206_2.png) [@Stevie-Kv](https://community.hubspot.com/u/Stevie-Kv)\
**Post date:** [October 8, 2020, 10:26am UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/86 "2020-10-08T10:26:14Z")

</div>

Hey guys, just thought I’d add an extra idea ontop of this.  
It would be good to also be able to create a dependent field based on the answers of 2 or more fields.  
If field A is X and field B is Y, show field C

---

<div class="post-metadata">

**Author:** ![tuyennguyen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/tuyennguyen/32/48165_2.png) [@tuyennguyen](https://community.hubspot.com/u/tuyennguyen)\
**Post date:** [October 20, 2020, 10:24am UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/87 "2020-10-20T10:24:35Z")

</div>

I really want this, so any process on this?

---

<div class="post-metadata">

**Author:** ![NachoLexidy](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nacholexidy/32/105324_2.png) [@NachoLexidy](https://community.hubspot.com/u/NachoLexidy)\
**Post date:** [November 26, 2020, 9:35am UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/88 "2020-11-26T09:35:23Z")

</div>

yes please! this is super necessary, we don’t want to pay typeform or other companies with logic-forms, we prefer to keep it all in one place in our HS account. Thank you!

---

<div class="post-metadata">

**Author:** ![KAnda](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kanda/32/86357_2.png) [@KAnda](https://community.hubspot.com/u/KAnda)\
**Post date:** [January 7, 2021, 9:53pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/89 "2021-01-07T21:53:25Z")

</div>

Any update? My entire company would benefit from this feature. It would make our customer onboarding form possible.

---

<div class="post-metadata">

**Author:** ![AKCologne](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/akcologne/32/22074_2.png) [@AKCologne](https://community.hubspot.com/u/AKCologne)\
**Post date:** [January 11, 2021, 9:42am UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/90 "2021-01-11T09:42:16Z")

</div>

We totally agree with KAnda and all others! We would have an immense benefit from this feature and would be happy to have any update on this!

---

<div class="post-metadata">

**Author:** ![EmiliaModolo](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/emiliamodolo/32/60590_2.png) [@EmiliaModolo](https://community.hubspot.com/u/EmiliaModolo)\
**Post date:** [January 11, 2021, 12:48pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/91 "2021-01-11T12:48:25Z")

</div>

Hi HubSpot community team 😊  
This would be a major improvement to forms, I’d like to have multiple levels too since they would allow me to better filter and categorize incoming leads with only one form instead of many.  
I would also like to volunteer in case the HubSpot Product Team needs testers.  
Wishing you all a great week,  
Emilia.

---

<div class="post-metadata">

**Author:** ![TRosic](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/trosic/32/31851_2.png) [@TRosic](https://community.hubspot.com/u/TRosic)\
**Post date:** [January 21, 2021, 1:59pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/92 "2021-01-21T13:59:06Z")

</div>

Incredible that the request exists for years now, but aside from merging of the same request and “being reviewed” status, not much has been done. Any progress on this idea?

---

<div class="post-metadata">

**Author:** ![EmilyWade](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/emilywade/32/59606_2.png) [@EmilyWade](https://community.hubspot.com/u/EmilyWade)\
**Post date:** [February 1, 2021, 10:49am UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/93 "2021-02-01T10:49:13Z")

</div>

A great idea - we could use this too!

Our example is that Field A containing “123” prompts the dependant Field B to appear. If Field B contains “456”, another Field C is prompted to appear to allow the user to specify more details.

---

<div class="post-metadata">

**Author:** ![sarahosell](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sarahosell/32/81360_2.png) [@sarahosell](https://community.hubspot.com/u/sarahosell)\
**Post date:** [February 11, 2021, 7:07am UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/94 "2021-02-11T07:07:29Z")

</div>

Really need this - we got Hubspot because we were excited about the forms but we may have to go back to using Google Forms for this basic feature.  
**4yrs of this feature request … ?**

---

<div class="post-metadata">

**Author:** ![DWinterburn](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dwinterburn/32/81360_2.png) [@DWinterburn](https://community.hubspot.com/u/DWinterburn)\
**Post date:** [March 3, 2021, 9:55am UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/95 "2021-03-03T09:55:26Z")

</div>

likewise, would be really useful.

---

<div class="post-metadata">

**Author:** ![RGarcia4](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rgarcia4/32/81360_2.png) [@RGarcia4](https://community.hubspot.com/u/RGarcia4)\
**Post date:** [March 4, 2021, 7:05pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/96 "2021-03-04T19:05:42Z")

</div>

YESSSS please!

---

<div class="post-metadata">

**Author:** ![lindseygarrett](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lindseygarrett/32/43872_2.png) [@lindseygarrett](https://community.hubspot.com/u/lindseygarrett)\
**Post date:** [April 15, 2021, 2:59pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/97 "2021-04-15T14:59:58Z")

</div>

Any update on this Hubspot? Last update from the product team was almost a year ago!  
I realize it might not be a “simple” solution, but I will reitterate the challenges we have with country and state/providence pick lists for being a global company. There is no way to maintain hundreds of complicated dependency rules [if Canada, show these providences, if U.S. show these states, etc.] per form AND the workflows to then put the correct data in the native fields so the data integrates with other systems like Salesforce.

A state/country combo is basic, and has been available on simple form systems for 15+ years. 😒

There are also tons of comments on this thread about various other uses that need these dependencies. Let’s make it a priority!

---

<div class="post-metadata">

**Author:** ![YiRui\_Chua](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/yirui_chua/32/23766_2.png) [@YiRui\_Chua](https://community.hubspot.com/u/YiRui_Chua)\
**Post date:** [April 16, 2021, 7:40am UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/98 "2021-04-16T07:40:38Z")

</div>

Hi team,  
Commenting for a customer here.  
Wondering if we have any updates on this? How I envision dependent fields to work would be similar to workflow (if/then) branch.  
I can think of many possible situations where dependent form fields will be super useful as compared to \> writing the condition within the form question itself OR setting up multiple forms as a workaround.  
Would love an update, thanks (:

---

<div class="post-metadata">

**Author:** ![PThomas](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pthomas/32/27794_2.png) [@PThomas](https://community.hubspot.com/u/PThomas)\
**Post date:** [April 22, 2021, 7:33pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/99 "2021-04-22T19:33:22Z")

</div>

This is a feature we really need! Right now we are using smart rules on landing pages to ask multiple layers of questions and it is an incredibly frustrating work around.

---

<div class="post-metadata">

**Author:** ![paju](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/paju/32/14727_2.png) [@paju](https://community.hubspot.com/u/paju)\
**Post date:** [May 10, 2021, 8:37pm UTC](https://community.hubspot.com/t/multi-level-dependent-fields/1558/100 "2021-05-10T20:37:59Z")

</div>

Currrently struggling to set up Gravity Forms and Zapier to feed data into Hubspot, since I need more dependencies than HS forms support. Really missing the ability to have multiple dependent fields. The need for this is driven by the criteria used by our sales management to allocate leads.

[Previous page](https://community.hubspot.com/t/multi-level-dependent-fields/1558.md?page=4)

[Next page](https://community.hubspot.com/t/multi-level-dependent-fields/1558.md?page=6)
