Migrated from legacy feedback forum with 169 votes.
I'd like to have more than 1 level in the dependent fields in forms.
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
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.
We really need this feature!
Currently we use embedded Cognito Forms which is far from ideal.
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
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.
It would indeed be really helpful to have this feature!
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.
Totally agree, it would be useful to add Rich Text box to the field also. Make it look a little more professional.
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?
I need this solution in my account.
yes please, us too!
Please hubspot add this
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
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.
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!
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.
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?
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.
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.
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.
ここにコメントを追加するには、ご登録いただく必要があります。 ご登録済みの場合は、ログインしてください。 ご登録がまだの場合は、ご登録後にログインしてください。