Conditional/Dynamic Dependant Dropdown Properties in forms and CRM
Dependant form fields are a great way of showing users different form fields/properties based on their selection in another.
In some situations, however, we really need to be able to show a subset of the values within one property based on the selection in another.
For this we need to be able to create rule-based, conditional or dynamic dropdown fields that are also dependant on other properties.
Forms are one use case for this, but some users also wish this was supported in the CRM UI, to assist internal users in making the right selections quickly.
👋Hi all! Rachel from the HubSpot Product team here. Both Conditional Property Logic (surface/require properties depending on the value of another property) and Conditional Property Options (specify which options are shown for a property depending on the value of another property) are out to all Hubs, Professional+ subscription.
👋Hi all! I’m Rachel from the HubSpot Product team. An update for you - we are now in private beta for Conditional Property Logic, a feature that will enable you to surface/require properties depending on the value of another property. This logic will be triggered when users make edits to properties across the CRM - specifically, in the ‘create record’ form, on the record page, and on the index page. If a property is required, users will not be able to save their changes until the required property has been filled.
Separately, we are also in private beta for a feature called Conditional Property Options. This feature enables admins to specify which options are shown for a property depending on the value selected for another property. During the initial beta period, this feature will only be enforced in the ‘create record’ form: When a user creates a record, they will be prevented from saving the new record if an incorrect option is selected based on the admin’s configuration.
Both features are available for all Hubs, Professional+ subscription. Your Customer Success Manager can request access to either beta on your behalf. We plan to moving these features to public beta in the near future based on usage and customer feedback, at which point customers will be able to opt in themselves. Thank you all for your feedback!!
Update, 2/1: Due to an enthusiastic response, this research study is now fully booked. Thank you all for applying!
Previous message is below:
___
Hi everyone! My name is Kyle and I’m a Product Designer at HubSpot. Good to meet you!
Some good news: we’re aiming to add new functionality that will allow you to define conditional options for fields. With this, you'll be able to show options in one field based on a chosen option in another field. Based on what I’ve been reading here, I think this would solve many of your needs. But first, we have to test it to make sure it’s easy to use and understand. That’s where you come in.
Would any of you be interested in participating in a paid user research study, testing Conditional Property Options? In order to ensure that this feature is effective and easy-to-use, we need to test it with you, our users. That will help us understand how well it works and meets your expectations.
Session details:
- Participants will be paid upon completion of the session - Session will require no more than 45 minutes of your time. - Session will consist of a recorded Zoom call where you’ll complete tasks using a prototype of this new feature - You’ll be asked to provide honest feedback as you go
Interested? Please sign up using this Google Form . If you qualify, we’ll reach out to set up a time to talk. Thank you, this study is now fully booked.
Once you’ve submitted the form: If you qualify, you’ll receive an email within the next 48 hours with the subject, “Schedule a HubSpot UX Research Session”. Just pick a time and we'll do the rest. We’re looking forward to sharing this prototype with you and gathering your feedback.
Any news on this? We need this for Sectors and Industries. The ones provided by Hubspot are too granular and do not fit our needs.
We want to create two drop downs, one for the sector and one for the industry. Depending on the sector, a preset list of industries will be available in the industry field. Now we need to select between 150 industries to get it right, and most of the time it is not correct.
This is standard CRM functionality that we need! In order to ensure data quality, you need to be able to limit the number of dropdown options in a second field based on the first, e.g. to track a sub-industry, a sub-service category, etc. Without this functionality, users will constantly enter bad data since it's not easy to know which categories belong together and which don't.
Update, 2/1: Due to an enthusiastic response, this research study is now fully booked. Thank you all for applying!
Previous message is below:
___
Hi everyone! My name is Kyle and I’m a Product Designer at HubSpot. Good to meet you!
Some good news: we’re aiming to add new functionality that will allow you to define conditional options for fields. With this, you'll be able to show options in one field based on a chosen option in another field. Based on what I’ve been reading here, I think this would solve many of your needs. But first, we have to test it to make sure it’s easy to use and understand. That’s where you come in.
Would any of you be interested in participating in a paid user research study, testing Conditional Property Options? In order to ensure that this feature is effective and easy-to-use, we need to test it with you, our users. That will help us understand how well it works and meets your expectations.
Session details:
- Participants will be paid upon completion of the session - Session will require no more than 45 minutes of your time. - Session will consist of a recorded Zoom call where you’ll complete tasks using a prototype of this new feature - You’ll be asked to provide honest feedback as you go
Interested? Please sign up using this Google Form . If you qualify, we’ll reach out to set up a time to talk. Thank you, this study is now fully booked.
Once you’ve submitted the form: If you qualify, you’ll receive an email within the next 48 hours with the subject, “Schedule a HubSpot UX Research Session”. Just pick a time and we'll do the rest. We’re looking forward to sharing this prototype with you and gathering your feedback.
Yes, I need this too, please make this available in the starter package. It would make me switch from free to starter. It's good to see that the product team is working on it. How will I know that this feature is available?
Responding here to stay updated. We are very interested in this feature and would like to be include for any Beta trials or testing. Our use would be for Events. Multi tiered drop down would allow us to select event and then select if they were invited, cancelled or attended.
What's the update on conditional dropdowns please? Our examples of requirement include:
Region? <-Drop Down
. Americas
. EMEA
. Asia
Country? <-Drop down
. Canada
. France
. Mexico
. Thailand
. Japan
. Germany
We need to have the 'Country' dropdown only show 'France' and 'Germany' as choices if the 'Region' dropdown was set to EMEA, and only have 'Canada' and 'Mexico' show is 'Americas' was chosen in the 'Country' dropdown.
This is just an example. We have several other 'conditional' dropdown we'd like to have, where the second dropdown filters the choices available based on the answer to the first dropdown.
It seems this feature has been asked for in various threads for at least 4 years, in this thread for a couple of years, and with a promising note that things were finally hapening in January '23.... but where is the fueture! Is there at least an 'expected by..." date?
👋Hi all! I’m Rachel from the HubSpot Product team. An update for you - we are now in private beta for Conditional Property Logic, a feature that will enable you to surface/require properties depending on the value of another property. This logic will be triggered when users make edits to properties across the CRM - specifically, in the ‘create record’ form, on the record page, and on the index page. If a property is required, users will not be able to save their changes until the required property has been filled.
Separately, we are also in private beta for a feature called Conditional Property Options. This feature enables admins to specify which options are shown for a property depending on the value selected for another property. During the initial beta period, this feature will only be enforced in the ‘create record’ form: When a user creates a record, they will be prevented from saving the new record if an incorrect option is selected based on the admin’s configuration.
Both features are available for all Hubs, Professional+ subscription. Your Customer Success Manager can request access to either beta on your behalf. We plan to moving these features to public beta in the near future based on usage and customer feedback, at which point customers will be able to opt in themselves. Thank you all for your feedback!!
👋Hi all! Rachel from the HubSpot Product team here. Both Conditional Property Logic (surface/require properties depending on the value of another property) and Conditional Property Options (specify which options are shown for a property depending on the value of another property) are out to all Hubs, Professional+ subscription.
Você deve ser um usuário registrado para adicionar um comentário aqui. Se você já estiver registrado, faça logon. Se você ainda não estiver registrado, registre-se e faça logon.
