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. It is now possible to add multiple-level dependent fields using conditional logic in the new forms editor.
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. It is now possible to add multiple-level dependent fields using conditional logic in 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!
I’m Sabari, the Product Manager for HubSpot’s Forms product.
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 extremely important and covers a range of use cases mentioned in the ideas forum.
We are yet to begin working actively on this feature. Once we get started I will keep this thread updated. Please stay tuned.
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
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
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."
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.
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.
HubSpot could really grow the power of Forms by letting people use multiple levels of depth with dependent fields to display the next question once someone has filled out the previous one. We have lengthy forms on our site (e.g. client questionnaires) and it would be great to reveal the next question or section of questions after they've filled out some of them. While a many-question form may appear overwhelming to a client at first, a cascading form would make for a much better experience.
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?
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.)
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.
