At present, HubSpot "Dependent Fields" can serve new form fields based on a selection made in a previous form field.
"Conditional Logic", however, serves different form fieldoptions based on a selection made in a previous form field. This is an important distinction as it requires only one "Property" for the options, regardless of the initial form field selection.
If I'm not clear, here's an example:
Property 1: Location
Property 2: Duration
User selects from a Location dropdown. Location options are "Madrid" or "London". We only offer "4 Weeks" and "6 Weeks" for "London", but offer "4 Weeks" or "12 Weeks" for "Madrid".
"Dependent Fields" will serve Duration upon a Location selection, but all options will be shown, even though we do not offer all Duration options for both Locations.
HubSpot recommends we create a new "Property" for each Location. This is not feasible when there are many Locations.
"Conditional Logic" simply serves the appropriate form field options based on the Location selected. So when selecting "London" the options shown would be "4 Weeks" and "6 Weeks", and for "Madrid" only "4 Weeks" or "12 Weeks" would be shown, but they would all populate the same "Property". Duration.
I’m Ian, the Product Manager for HubSpot’s Forms tool.
Thank you all for taking the time to submit, upvote, and comment on this Idea. We've now added conditional logic to the new forms editor. You can request to join the beta through Product Updates.
I’m Ian, the Product Manager for HubSpot’s Forms tool.
Thank you all for taking the time to submit, upvote, and comment on this Idea. We hear you loud and clear, and we agree that this functionality is important. We are currently evaluating how our team will implement this idea. If you're interested in participating in user testing, just reply to this thread.
Any news about this feature request will be relayed on this thread, so stay tuned!
This is tablestakes functionality as far as form builders go. I'm coming from other CRM and marketing automation solutions and am blown away that Hubspot's form builder is so oversimplified and feature anemic.
Any update on this, @JoeMayall ?? Lots of people are having to use 2 platforms because of this issue just to support their needs. It's required in order to handle the most basic of event registrations, meaning automation also has to be supported on another platform, and an extra step in recording contact information.
I am losing faith in Hubspot. @JoeMayall are you still here? This idea was first raised in October 2019 and we are 3 weeks away from October 2022...nearly 3 years and yet still no progress. Is this in your product pipeline or not? At least acknowledge if it is or if it is not in the pipeline for those of us who need to evaluate whether to stay with Hubspot or look for alternate solutions.
Adding in the importance of this for us. It would be great to have dependent fields on our dependent fields. We have multiple levels of product and being limited to only one property has made us use additional properties or forego collecting some data in service of a customer experience. Please fix!
+1 - Another use we have is for our warranty claim forms. If someone enters a product SKU into a field, we use dependent fields for serial number and reason for return. The form has the ability to include 1 product or up to 10 products. I would like to make serial number and reason for return required IF Product/SKU is known for each of the 10 sections for different products.
I'm having the same issue as well. Our team needs to be able to select specific options that are dependent on previous answers. For example, if someone selects "Yes" to a specific contact property, there needs to be functionality that allows for multi-conditional options. This feature should be implemented into the forms, as its' needed for various sales staff.
Wondering if there is any update on this? We're needing to migrate across from gravity forms into HS but need option for multiple drop down levels of logic.
I gave up waiting and instead have used CRM perks plugin to transfer data from Gravity Forms to Hubspot and it seems to work well once you have the settings and fields mapped.
We have to run a mix of HubSpot and Gravity forms to cover our needs due to limitations of HS forms. This then results in needing to use 3rd party "middleware" to get the data into HubSpot in a meaningful way.
It would be great if HS forms became more feature rich so we could remove the middleware step, which would improve our return on investment in HS and reduce our system admin overhead to keep the connection manitained.
