Creating properties and sub-properties (sub-categorys)

[LLampe]

When creating deals, I want to add a number of properties under the heading product/service. Now I want a subcategory again for a number of these properties.

So for example you can choose under product/service:

- Service 1

- Service 2

- Service 3

And when you choose service 1 you can select:

- subcategory 1

- subcategory 2

Or when you choose service 2 you can select:

- subcategory 1

- subcategory 2

What's the best way to set this up?

[TomM2 · Accepted solution]

Hey @LLampe if this is for properties for users to use within your CRM, it's not currently possible to have sub groups for properties. You can only have 1 group for your properties to group them in. 

However, if you're looking to create these as questions for when someone is creating a contact there may be features to achieve what you want. 

If you're looking to have visitors see these within forms and have fields only show depending on other fields the dependent field feature in forms would be what you're looking for. 

If you're looking to have these display when a user is creating a contact within HubSpot, then additional logic on mandatory properties would help you achieve this! 

If this is just for organisation purposes then there would currently be no way to have sub-groups for properties when creating them. 

[karstenkoehler · Accepted solution]

Hi @LLampe,

You'd navigate to Menu > Reports > Reports > Create report > Custom report builder and select Deals as primary data source.

You would then set up your report like this:

In my case, Deal type is property 1, Original source type is property 2. Amount is the revenue.

Best regards!

[karstenkoehler · Accepted solution]

Hi @LLampe,

Great news, dependend properties are 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)
• Index page board view
• ‘Create record’ form

Demo Video

Who gets it?

All Hubs, Professional+ subscription.

---

If you're on a Professional or Enterprise subscription and you're not seeing these options yet, you should be able to opt into the beta here:

If you're not seeing the beta there, it'll probably appear in the next few days.

Have a wonderful day!

[TomM2 · Accepted solution]

Hey @LLampe if this is for properties for users to use within your CRM, it's not currently possible to have sub groups for properties. You can only have 1 group for your properties to group them in. 

However, if you're looking to create these as questions for when someone is creating a contact there may be features to achieve what you want. 

If you're looking to have visitors see these within forms and have fields only show depending on other fields the dependent field feature in forms would be what you're looking for. 

If you're looking to have these display when a user is creating a contact within HubSpot, then additional logic on mandatory properties would help you achieve this! 

If this is just for organisation purposes then there would currently be no way to have sub-groups for properties when creating them. 

[karstenkoehler]

Hi @LLampe,

Unfortunately, this is not possible at this stage. HubSpot doesn't have any features for this kind of dependency/hierarchy.

The best workaround that I've found is to use very descriptive values, e.g.

Property 1

- "Value 1"

- "Value 2 (please specify in Property 2)"

- "Value 3"

- "Value 4"

- "Value 5 (please specify in Property 3)"

Property 2

...

Property 3

...

Far from ideal because the dependent fields cannot be made required – since they don't apply to all values in property 1 –, but better than nothing.

Another option would be to include all options in one level of hierarchy, again not ideal, since it doesn't work well in reports, but I wanted to share this option as well.

"Value 1"

"Value 2 – Sub-value 1"

"Value 2 – Sub-value 2"

"Value 3"

...

Other users have already requested a feature from the product team: https://community.hubspot.com/t5/HubSpot-Ideas/Dependent-Properties/idi-p/420732

The product team reviews these requests based on their popularity, I'd recommend upvoting and commenting.

You can also help other users to find this request more easily by accepting my reply as a solution. I'd appreciate it, too. It helps me allocate more of my time to helping other HubSpot users in the community.

Have a great day!

[LLampe]

Hi Karsten,

Thank you for this input! The reason we want to be able to see this in a deal, is because we eventually want to create a dashboard where you can see these different properties and what the revenue is for each property. Do you have any idea what the best way is to do that?

[karstenkoehler]

Hi @LLampe,

For reporting, these properties wouldn't have to be dependent. You would of course have the issue of some users ignoring the fields, but for report creation itself, they don't have to be dependent / required.

In the report builders, there is always the option to "link" properties by choosing one primary property and breaking down the report by a secondary property.

The revenue would be a third one, so the best way to display this would be a pivot table in the custom report builder. This would give you the revenue by property 1, broken down by property 2.

Let me know if you need exact steps to create this report.

In any case, it's not possible to create dependent required properties in the CRM UI.

Best regards!

[LLampe]

Exact steps would be amazing! Because maybe if I can make this happen, the subcategorys are not neceserry. Our goal is seeing the revenue, so that would be great! 

[karstenkoehler · Accepted solution]

Hi @LLampe,

You'd navigate to Menu > Reports > Reports > Create report > Custom report builder and select Deals as primary data source.

You would then set up your report like this:

In my case, Deal type is property 1, Original source type is property 2. Amount is the revenue.

Best regards!