[Rolling out now] Unique Value Enforcement on Properties
Apr 27, 2022
What is it?
It's happening! You can now enforce uniqueness on properties in order to prevent duplicate values.
Why does it matter?
Two words: data quality. You rely on the data you store in HubSpot to make timely and critical business decisions, so it's important that the data is clean and reliable. One of the most critical aspects of having clean and reliable data is uniqueness—i.e., ensuring there are no duplicate records.
Until now, HubSpot has used the email property on contact objects to avoid duplicate records. We've heard loud and clear that admins need to enforce uniqueness on other objects in order to improve their data quality. With this release, admins can now set newly created custom properties as unique through the UI for HubSpot standard objects (companies, deals, products, and tickets), as well as custom objects.
How does it work?
Follow these simple steps to start enforcing uniqueness on a property:
In your HubSpot account, navigate to Settings > Properties.
Select one of the following objects from the dropdown: Company, Deals, Products, Tickets, or any Custom Object.
Then select Create Property.
Within the property creation flow, select either "Single-line text" or "Number" as the Field Type.
Next select the "Require each value for this property to be unique" checkbox and click the Create button to create the property.
When uniqueness has been enforced on a property, users will be prevented from entering duplicate values and will see the following error message when attempted:
Please note there are a few limitations to this feature:
Uniqueness can only be enforced on companies, deals, tickets, and custom object properties. It CANNOT be enforced on contact object properties.
It can only be set for newly created single-line text or number properties. Customers will not be able to set this validation on existing properties.
There is a limit to the number of properties the validation can be applied: 10 per standard object and 2 per custom object.
Who gets it?
This feature is rolling out now and will be available to all accounts.
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
[Rolling out now] Unique Value Enforcement on Properties
Apr 27, 2022
What is it?
It's happening! You can now enforce uniqueness on properties in order to prevent duplicate values.
Why does it matter?
Two words: data quality. You rely on the data you store in HubSpot to make timely and critical business decisions, so it's important that the data is clean and reliable. One of the most critical aspects of having clean and reliable data is uniqueness—i.e., ensuring there are no duplicate records.
Until now, HubSpot has used the email property on contact objects to avoid duplicate records. We've heard loud and clear that admins need to enforce uniqueness on other objects in order to improve their data quality. With this release, admins can now set newly created custom properties as unique through the UI for HubSpot standard objects (companies, deals, products, and tickets), as well as custom objects.
How does it work?
Follow these simple steps to start enforcing uniqueness on a property:
In your HubSpot account, navigate to Settings > Properties.
Select one of the following objects from the dropdown: Company, Deals, Products, Tickets, or any Custom Object.
Then select Create Property.
Within the property creation flow, select either "Single-line text" or "Number" as the Field Type.
Next select the "Require each value for this property to be unique" checkbox and click the Create button to create the property.
When uniqueness has been enforced on a property, users will be prevented from entering duplicate values and will see the following error message when attempted:
Please note there are a few limitations to this feature:
Uniqueness can only be enforced on companies, deals, tickets, and custom object properties. It CANNOT be enforced on contact object properties.
It can only be set for newly created single-line text or number properties. Customers will not be able to set this validation on existing properties.
There is a limit to the number of properties the validation can be applied: 10 per standard object and 2 per custom object.
Who gets it?
This feature is rolling out now and will be available to all accounts.
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Why is it that there is always a weird restriction like "CANNOT be enforce on contacts"?? Like what am I using a CRM for?? ITEMS???? How technically hard can it be to enforce uniqueness of a property? You are either using a relational DB or nosql, whatever the tech underlying hubspot, it shouldn't be this hard and you shouldn't be "Rolling it out" like it's some new feature..
Is it possible to have this behaviour adopt the new value and overwrite the old one? As I understand it, this prevents the new record being created and preserves the old one. Is this correct? Thanks.
