La fonction de suggestion automatique permet d'affiner rapidement votre recherche en suggérant des correspondances possibles au fur et à mesure de la frappe.
Deal doesn't enroll in workflow after associated company is merged with another
Résolue
Hey,
I am trying to require that all deals are associated to a company that has a property 'HQ Company ID' = known, before they can be moved to closed won. We are a SAAS company, and this HQ Company ID is the product account unique identifier.
Since (to my knowledge) you can't require any specific associated object data before moving deals between pipeline stages, the solution I tried was to create a Deal property ('HQ Company ID (Deal)') which would be automatically populated with the 'HQ Company ID' value from the associated Company right away when it is known through a workflow(see the workflow below), and then set up a requirement in the relevant pipeline that this deal property needs to be known before moving the deal to Won.
This generally worked fine, but it seems to break when the associated company only has the 'HQ Company ID' populated after a merge with another company. That regularly happens in cases where the deal/opportunity is generated by a rep through cold outbound. In those cases the deal is initially associated with a company that has no HQ Company ID since they don't have an account in our product. But at a point during the sales process they create an account in our product, and when that happens we automatically create a company in Hubspot which includes the HQ Company ID for that product account.
The process I felt was logical at that point was that the rep would go and manually merge these two companies together. The open deal would, after that merge, have an associated company with the 'HQ Company ID' property known. I thought this would work, but apparently the workflow I described does not trigger if the change Company property updated via a merge, so the deal property for HQ Company ID does not get updated in this case. According to Hubspot's support this is the intended behaviour.
I'm curious if there are any other ways you think we can set this up to achieve our goal of requiring that a deal has a connected HQ Company ID before it's marked won? Any workaround or process change ideas would be greatly appreciated.
Deal doesn't enroll in workflow after associated company is merged with another
Résolue
Hey @hafsteinnbg, thank you for posting in our Community!
You could Implement validation checks within your pipeline stages to ensure that the 'HQ Company ID' is populated before allowing deals to progress to the closed won stage. This could involve manual verification by the sales team or automated checks using custom scripts.I would recommend connecting with HubSpot Technical Support, as Support is included in your subscription and they will be able to provide real time assistance for this matter, including hopping on a screenshare if necessary.
Deal doesn't enroll in workflow after associated company is merged with another
Résolue
Hey @hafsteinnbg, thank you for posting in our Community!
You could Implement validation checks within your pipeline stages to ensure that the 'HQ Company ID' is populated before allowing deals to progress to the closed won stage. This could involve manual verification by the sales team or automated checks using custom scripts.I would recommend connecting with HubSpot Technical Support, as Support is included in your subscription and they will be able to provide real time assistance for this matter, including hopping on a screenshare if necessary.