Considering that for Contacts and Companies, the Primary identifier is the email address, now, when we create a custom object (like cars, course and so on…) clearly these objects cannot have an email address field, but other custom fields.
And so in a simple logic to avoid duplicates when a user try to insert a new custom object, we need to decide what is the Primary identifier when we create a custom object.
Because now, with the actual logic, the custom objects are useless.
How hubspot is planning to fix this?
Yes the model probably worked fine many years ago for online shopping, but in today’s world, things have gotten more complex and often external CRM’s are being used to store data, which will contain the same email for multiple legitimate cases, therefore Husbpot ends up overwriting itself.
By a user simply choosing what the primary ID is, i.e. CRM unique id, this would allow an email to exist in several instances in Hubspot and the contact can be emailed based on different criteria as relevant.
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.
You could use a single text propert, select the “Require each value for this property to be unique” and then make it mandatory in the creation of the Custom Object