Nov 18, 202310:09 AM - edited Nov 18, 202310:10 AM
Contributor
Using associations (and their properties) as properties across multiple features
SOLVE
Background:
I'm new to HubSpot and trying to get a better understanding of what I can do with the data structure in HubSpot. We have Service Professional with all other modules at the Starter level.
Problem:
There are multiple areas where I expect to be able to display or use an association or property of an associated object but am unable to do so. This is preventing us from organizing our data in a way that is useful to us and creating effective workflows.
I realize that some of what I am expecting is related to a beta feature of company-to-company associations, but it doesn't seem limited to that association.
Examples:
I realize there are better ways to approach some of these examples, but I'm using them to illustrate the bigger confusion I'm trying to wrap my head around.
1) Workflow branch filter based on specific associated company attribute
I'm trying to create a workflow to assign a conversation owner.
I can set a workflow branch filter based on a contact's company name, but not the Company Owner.
2) Tickets view by parent company (using beta company-to-company association)
I'd like to create a tickets view to group tickets by parent company.
I can add a column with the company name, but not any of that companies properties (including the associated parent company).
Even if I could, I can't even sort by associated company, so I'm not sure I could sort by Parent company if shown.
3) Reporting on number of deals of child companies per parent company
I'm able create a pivot table report with parent companies as rows by filtering companies by # of child companies.
I'm not able to use measures of the associated child companies. In this example the parent and child each had a separate deal, but only the parent deal is counted.
I would appreciate your thoughts. The data model itself seems robust, but I'm feeling very limited in what I can actually do with it.
Using associations (and their properties) as properties across multiple features
SOLVE
Here's what I can offer:
#1 - The owner you are looking for is under the Company fields. Change your filter to Company.
A company can have an owner and associated Contacts can each have a different owner. Think of it like our company president owns the record at the Company level, but different contacts work for different departments, so our sales people own the Contacts associated with their respective departments. But the President, the Company Owner, oversees that everyone is getting taken care of.
#2 - We don't use Hubspot tickets. But, I wonder if you change your filter to Company, instead of Tickets, if you'll find the fields you're looking for.
#3 - Hopefully one of the other experts can jump in on this one.
Best of luck!!!
*************************** Did my post solve the questions or challenge? Please mark it as a solution for others to find.
Using associations (and their properties) as properties across multiple features
SOLVE
Here's what I can offer:
#1 - The owner you are looking for is under the Company fields. Change your filter to Company.
A company can have an owner and associated Contacts can each have a different owner. Think of it like our company president owns the record at the Company level, but different contacts work for different departments, so our sales people own the Contacts associated with their respective departments. But the President, the Company Owner, oversees that everyone is getting taken care of.
#2 - We don't use Hubspot tickets. But, I wonder if you change your filter to Company, instead of Tickets, if you'll find the fields you're looking for.
#3 - Hopefully one of the other experts can jump in on this one.
Best of luck!!!
*************************** Did my post solve the questions or challenge? Please mark it as a solution for others to find.
For your workflow, it's because it's based on contact, so options as company property will be limited. I recommend creating workflow branches to send enrolled objects down multiple paths based on specific conditions. (more information here) This way you can enroll these contacts to a company workflow and pull the information of the company owner based on these contacts that were on the previous contact workflow.