I’m a HubSpot partner and I have encountered an instance where my HubSpot customer wants to use the county as a routing option for internal emails. That’s great and doable; however, when the customer has nearly two hundred offices around the country, this leads to an overwhelming number of counties listed for a customer to choose from on the form.
Our idea: Use conditional options! By having a State dropdown menu and creating a dropdown for County, we could apply the conditional option for each state.
The Result: The conditional option only works on the contact record and not on forms.
Agreed, I have something similar (and we’re based in Virginia too). So being able to put conditional options on forms would get us to using HubSpot forms rather than Google.
I have a list of job responsibilites on a form… then we want to know their PRIMARY responsibilty. Instead of showing ALL of the options again, it only makes sense to show from the seleted options they picked above on the job responsibilites question. This conditional logic on forms would be very helpful.
I agree, only convention I can use now is to have a logic under every dropdown and create each property as an option. It’s a waste of Custom Property and a bit long for forms (logic), specially on cases that have a lot under their dropdowns.
Crossing my fingers this awesome new feature rolls out to forms soon!
We work with lots of clients where their properties and data get out of control, and it’s an expensive exercise to clean it up. Without this conditional property, we have, for example:
Property: List of Options A
Property: List of Options B
Property: List of Master Options
Workflow: Copy A or B to Master Property
In a portal with a lot of users, there is additional work required to maintain unnecessary extra assets and risks that the wrong property will be used in reporting, that an option could be added to A which isn’t then updated in the master property and breaks the workflow, that the Master property is added to a form instead and then the List A and B properties become disparate etc.
With conditional logic available on forms, we just need:
Property: List of options
This one property with conditional logic set by a controlling property centrally maintains and enforces consistency wherever data is collected. Reducing the number of workflows is also really helpful to reduce the noise in an activity record view and makes it much easier to trace back issues or to introduce new intiatives as there is less to audit or edit when doing so.
I feel positive about this being on the horizon… Keeping my eyes peeled
In a world where a large portion of our CRM data comes from submitted forms, this is absolutely critical functionality for conditional options on properties to actually work. Please consider this idea.
Having exactly the same issue at the moment. As it already works with the CRM I guess it would not be too difficult to implement it in other places as well.
How this isnt available is crazy, another use case that I have is for a client looking to use a HubSpot form as a booking form for an event. If an event is Online compared to in-person (travel requirements, recording function etc) the list of options as im sure you can imagine, will be massively different.
I have client that needs to set conditional dropdown values for operating systems on a ticket form based on the type of device. I knew that we could do this in the CRM, but I’m astounded this still isn’t possible for forms.
Another vote for the same logic you can control on the property level to also be available in the forms editor! PLEASE! ROADBLOCK/MASSIVE TIME CONSUMING WORKAROUND IN PROGRESS.
