Being able to surface data from one object on another object without the use of workflows has been a huge improvement.
However, now that the data can be visualized on the second object, our users often times need to be able to update it while on that object without leaving the object’s workscreen.
For example, we are syncing some key Company properties to the Lead Object so that data about the company stays evergreen but our sales teams can see that data in the leads tool while working their leads. It would be great if, as they engage with the lead, they had an easy way to update these values without having to leave the sales workspace. Currently it leads to some confusion when a property can not be edited due to it being a sync property - and even having a prompt that opens the appropriate Company property or something that tells them that the field needs to be updated on the Company object would be very useful in making sure data gets updated.
Ideally we’d be able to set sync rules the same way we do with other tools (such as data sync for integrations) but even just allowing for data to be updated in either object would help immensly!
+1. Perhaps a toggle within the Sync Property so admins can choose, per property, whether to enable two-way sync? Just in case there are certain properties where you actually want users to navigate to the original property for some reason.
Love this idea and would be super useful and I can think of many use cases!
There may be issues to overcome with access/permissions. EG, If I have access to edit all deals, but can’t edit companies and I have a 2-way rpoperty sync from deal <> companies, would I still be able to edit the property on the deal even though it effects the company? Perhaps this needs an additional setting such as over-rule access/permision limits
After spending 1-2 years setting up and configuring Hubpot, I’ve slowly come to realise that this is the single most biggest challenges in Hubspot. What we need is for a two way property sync accross all objects (or specified objects). Right now we have one way property sync recently released (we are on the right track!), but the ultimate problem solver is two way. This means that if a change is made to the deal property, it makes that same change to the contact, and whatever change is made to the contact, it makes that change to the deal. If the list of a property is updated on the deal within the property editor, that same list change is made to the contact as well. It’s a major challenge to constantly copy properties from one record to the other before sending off important texts or e-mails. The reason why we need this so badly is because certain actions can only be done on specific object types. For instance, when a text is sent, we usually have to send the text from the contact record, but we need deal based triggers, so we have to copy the deal properties to the contact before sending. This is one of countless examples.
I’m confident that the reason there are not 100+ likes on this one is because this particular need is VERY hard to spot early on in the setup phase, and because it’s still possible to achieve the desired outcome, but only with a ton of workflows that may need reconfiguring once we’ve realized that we’re not copying the property over to the appropriate record in time before sending off e-mails/texts, in which case we have to add delays to make sure it copys before it sends, or create the copying action right before it sends. It eventually becomes a nightmere that creeps up on you.
Hubspot is still amazing though : )
I’m Jeannie, and I’ve recently taken ownership of this product area.
Thank you for sharing your feedback and use cases around supporting bidirectional syncs for our sync properties. I know this capability would meaningfully improve certain workflows, and I appreciate everyone who has taken the time to comment and upvote.
At this time, this work is not currently planned, as we’re focusing our near-term roadmap on higher-impact areas within this product space. That said, your feedback is incredibly valuable, and I’ll continue to monitor this thread closely. As related initiatives evolve and we learn more from customers and partners, we may reassess this direction in the future.
Please keep the use cases and comments coming—they help us understand where this fits in your workflows and how we can best support you over time.
Thanks again for your continued engagement and partnership.
Thanks for the update @JeannieN. I do still think this would be a useful feature to have at some point. We sync Contact and Company properties to other objects, such as Deals, to surface key information. This saves users time when working on the Deal, but it would save even more time if they were able to edit these key properties when things change.
I agree with all on this thread. Having a two-way sync for properties shared on different objects would be tremendously helpful. It’s one of the biggest headaches I have managing the system--making sure that properties on one object contain the same value as another. The ability to edit in either object will reduce a tremendous amount of friction for record maintenance.
In addition, the property sync field can be inaccurate. I can’t tell you how many bad values I have becaused the sync pulled data from the wrong record because it was or wasn’t the first or most recent created.
Hello Community Members,