This is unfortunately currently not possible. The only workaround is currently trust-based: You would rename 'Manufactures' into 'Manufactures (please specify below)'. Someone who selects this would then be, hopefully, motivated to fill the second field, too.
I'd recommend upvoting and commenting on the idea. The product team reviews these requests based on their popularity. You can also help others find this request more easily by accepting my reply as a solution. (I'd appreciate it.)
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Great news, this is now a HubSpot feature! See the announcement below:
[Public Beta] Conditional Property Logic
Sep 28, 2023
What is it?
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)
Great news, this is now a HubSpot feature! See the announcement below:
[Public Beta] Conditional Property Logic
Sep 28, 2023
What is it?
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)
This is unfortunately currently not possible. The only workaround is currently trust-based: You would rename 'Manufactures' into 'Manufactures (please specify below)'. Someone who selects this would then be, hopefully, motivated to fill the second field, too.
I'd recommend upvoting and commenting on the idea. The product team reviews these requests based on their popularity. You can also help others find this request more easily by accepting my reply as a solution. (I'd appreciate it.)
Best regards!
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
