We’ve recently noticed an unexpected change in how seat associations are being handled in our integration. Our system detected that seats are now being associated using two different types:
1. Standard association type: “2-39766996”
2. Custom association type: “p40098205_seats”
This change caused some disruption in our service as some seats were only visible through the new custom association type (“p40098205_seats”), while others remained on the standard association (“2-39766996”).
Specific questions:
1. Was this change part of a planned update? If so, could you point us to any documentation about this change?
2. Is there a specific reason why some seats use the custom association type while others use the standard type?
3. Should we expect all seats to eventually migrate to the new custom association type (“p40098205_seats”)?
4. What is the recommended approach for handling seat associations moving forward?
I am using custom objects under deals
Before: Only looked for seats in one association type
After: Added checks for both association types and deal associations:
if seats := hubspot_data.get(“associations”, {}).get(“2-39766996”, {}).get(“results”, []):
hs_seat.extend(seats)
if seats := hubspot_data.get(“associations”, {}).get(“p40098205_seats”, {}).get(“results”, []):
hs_seat.extend(seats)
previously accessed with “2-39766996”
Now I am getting if I use this association “p40098205_seats”
We’re you able to get this resolved with support? — Jaycee