Missing associations in v3

Hi all,

we running into an issue with the instance of one of our customers.

We currently using Association V3 API

POST https://api.hubspot.com/crm/v3/associations/deal/company/batch/readAuthorization: Bearer xxxxContent-Type: application/jsonAccept: application/json{ "inputs": [ { "id": "xxxx" } ]}

Returns ONE relation.

Doing the same with v4 (just replacing v3 with v4, rest is the same), it returns TWO relations! In v3 the Deal to Company (not primary) seems to be missing, only getting back the deal_to_company type, which is the Deal to Company (Primary) in v4. But the additional relation from the not primary is missing.

This seems like a bug in v3. Is this a know issue? Or can/will this be fixed?

Otherwise upgrade our code to v4 is not an easy fix, because all exisiting configuration and data needs to be update as well, as we are using the type from v3 (in this example deal_to_company and deal_to_company_unlabeled), which then becomes type ids 5 and 341.

The old type is also not present in v4, so its hard to upgrade as well. Only way I found was using v3 to get the type id and then using v4 for the rest, but not sure when this breaks, when I mix v3 and v4…

Hey, @attrib :waving_hand: The v3 documentation mentions in several places (example) that there are differences in what can be used and what will be returned between the v3 and v4 endpoints. The v4 endpoints offer functionality that the v3 do not.

If you believe you have a verifiable and reproducible bug to report, you can do it here. Please note, this is not a support form and cannot be used to get 1-1 support. It is a form to report issues and give developer-related product feedback.

Best,

Jaycee