Store property based on association between two objects

I have a custom object (Location) that represents distinct locations that one of our HubSpot clients operate. Some companies represent vendors that provide goods and services to locations. Other companies are the clients that the location is operated on behalf of. In both cases, the association of a company and location is recognized via an account number. For example company A sells widgets to Location A, Location B, and Location C. I can create an association between Company A and Location A and Company A and Location B, etc. However, each of those association is represented by a distinct account number provided by Company A - an account number I need to reference in coorespondance. Right now we collect the account number in a playbook when Company A is onboarded, however, you can’t extract values from playbooks. I don’t want to create a property on the Company object either, because I would have to create a property for each location of which there are hundreds. Instead, when I associate Company A with Location A, I want to store the account number for that association. The only thing I can figure out is create another custom object for account numbers, but you can’t look-up other property values from other objects, so I don’t know that this will help. How would you solve this?

Hi @crothenberger,

Thanks for reaching out!

I would like to add a few of our subject matter experts to our conversation.

Hi @Josh, @himanshurauthan, @danmoyle - Do you have any thoughts or suggestions for @crothenberger?

Thanks!

Best,

Kristen

@crothenberger So if I’m understanding this, the Playbook only saves to 1 of the 4 standard HubSpot properties, correct? It looks like this is an Idea here where we can upvote and comment. HubSpot product managers pay attention to these.

I’m not sure of a solution other than possibly creating a workflow which would assign a task as soon as the association is made, which tells the person creating it to go in and fill out the custom object Location’s custom property of account number. A bit cumbersome, but seems to be the only thing my mind can come up with.

It isn’t just that we can only collect certain properties via the playbook, the issues is that the property we need to store isn’t a property of the location or the company - it is a property of the association.