Is there a way to create a property that is linked by conditional logic to another property.
i.e. I have a list of "general" issue, but I want the support team to be able to select sub issues when they select one of the entries for the general issue.
👋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 set conditional logic for enumeration properties. 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. This feature is available for all Hubs, Professional+ subscription.
Your Customer Success Manager can request access to this beta on your behalf. We plan to move this feature 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!!
Requiring the right data at the right time is critical to CRM data quality. Missing or incomplete data can throw off your ability to capture high-level insights or even take critical action based on information in a record. For example:
You want to capture the specific reasons why deals are lost
When a deal is closed/lost, users are required to select an option in Lost Category
They select ‘Product’ as the reason - but you want to know what types of Product-related reasons (bugs? incomplete functionality?)
Or another example:
You want to capture a customer’s billing information
When a user fills out Billing Method as Email, you want to require that they also fill in the Billing Email so you can bill the customer
Conditional property logic enables admins to show (and require) the right properties at the right time across the CRM. Today, in the ‘Customize the create record’ page, admins can set conditional logic for properties that have been added to the ‘Create record form. Now, admins will be able to set conditional logic for enumeration properties regardless of whether they have been added to the ‘create record’ form. This logic will be triggered when reps make edits to properties across the CRM.
If a property is required, users will not be able to save their changes until the required property has been filled.
Why does it matter?
Conditional property logic is a powerful tool to help you safeguard data quality and create a streamlined experience for reps interacting with records. This data management tool will help CRM admins lay the foundations for clean data and a smooth rep experience by guaranteeing that required information isn’t missing. And it will save time spent chasing down incomplete data.
How does it work?
HubSpot admins can set up conditional property logic in Property Settings > Conditional Property Logic tab.
These rules will be surfaced - alongside conditional stage properties- in the following places when a rep edits a property:
Record page highlight card, About section, association card, and ‘View All Properties’ page
Index page inline edit
Index page bulk edit (conditional stage properties will also now be enforced here)
Conditional logic for companies and contacts would make segmentation easier. It is essential for targeted marketing. Make it simple for our users when creating new entries!
We are also looking for something like this - we want users to select a location, and for conditional logic to then show the user the only appropiate options within a property. For example, user selects location A from dropdown and then have option to select marketing source property with options 1, 2 or 3. But if they select location B, the marketing source can be 4, 5 or 6.
This is definitely something needed. CRM platforms such as Salesforce have such customisable fields that allow an admin/developer to capture data using conditional logic. It is really disappointing that hubspot does not have this
Is it safe to assume this isn't available on the ticket object either?
Scenario: Category would be 'How Do I?', 'Technical Issue', 'Billing Issue' and then a custom property called 'Sub-Category' would be dependent on the Category field to a) become active for data entry and b) would dynamically allow values associated with the value selected in the Category property. This is pretty common in most ticketing systems and for most service organizations.