APIs & Integrations

claude191
Participant

Fetching associated companies for a deal is returning duplicates

SOLVE

Hi,

 

We use deals to process orders.  Our integration fetches a deal when it reaches a certain deal stage and pushes the details into our ordering systems.  We have been doing this for most of the past year.

 

However, starting very recently (maybe a few hours ago) we started receiving the same company twice as an association to a deal.  Here is the URL we fetched and the result:

GET https://api.hubapi.com/crm/v3/objects/deals/5236376468/associations/company?hapikey=secret
{"results":[{"id":"6057770041","type":"deal_to_company"},{"id":"6057770041","type":"deal_to_company_unlabeled"}]}

The same company is listed twice.  Can you assist?

However, for a different deal created a few hours before this one we get:
GET https://api.hubapi.com/crm/v3/objects/deals/5161733184/associations/company?hapikey=secret
{"results":[{"id":"5990234509","type":"deal_to_company"}]}


Any new deal we create now seems to return the associated company twice.

 

Thanks,

 

Claude.

 

1 Accepted solution
claude191
Solution
Participant

Fetching associated companies for a deal is returning duplicates

SOLVE

Update for anyone else readying this post - the problem appears to be resolved by a recently deployed hostfix.

View solution in original post

6 Replies 6
Klapprodt
Contributor

Fetching associated companies for a deal is returning duplicates

SOLVE

Was there any progress on this issue? At the moment I just drop duplicates based on the deal ID, but it is hard to check if there is overall info in the dropped duplicates, that may get lost. 

0 Upvotes
claude191
Participant

Fetching associated companies for a deal is returning duplicates

SOLVE

Hi,

 

It is some time ago, so my memory is hazy.  However, I did post in May '21 that HubSpot had deployed a hotfix and the problem was resolved.  Looking back at the support ticket, it seems to have been an error with the (at the time) new "flexible associations" changes.

 

Cheers,

 

Claude.

 

0 Upvotes
claude191
Solution
Participant

Fetching associated companies for a deal is returning duplicates

SOLVE

Update for anyone else readying this post - the problem appears to be resolved by a recently deployed hostfix.

dennisedson
HubSpot Product Team
HubSpot Product Team

Fetching associated companies for a deal is returning duplicates

SOLVE

Hi @claude191 

Looks like you also reported this directly to support which I believe was the correct course of action.  Looks like there is a fix being implemented.  Support should get back to you, but feel free to post here if you do not get a response soon and I will look into it 😀

0 Upvotes
GKasireddy2
Member

Fetching associated companies for a deal is returning duplicates

SOLVE

Hi dennisedson,

I have also getting same response for below request.

The same company id is listed twice in the response with type : 

deal_to_company,
deal_to_company_unlabeled
I don't need deal_to_company_unlabeled in the response.
Any suggestions?

https://api.hubapi.com/crm/v3/objects/deals?associations=companies

"associations": {
                "companies": {
                    "results": [
                        {
                            "id""8028943361",
                            "type""deal_to_company"
                        },
                        {
                            "id""8028943361",
                            "type""deal_to_company_unlabeled"
                        }
                    ]
                }
            }
0 Upvotes
claude191
Participant

Fetching associated companies for a deal is returning duplicates

SOLVE

Hi Dennis,  actually support kept telling me to report it here.  Which seemed odd - but I did so anyway.

 

I've not heard back from support.  Meanwhile our business has stopped because our integration cannot load duplicate companies from closed deals into our ordering system.  It is a very bad situation for us until we can get the integration altered or HubSpot fixed.

We also unimpressed with how HubSpot are handling this missiong-critical (for us) fault.