It would be very useful to be able to create cross-object properties, especillay for the following reasons:
- we will no longer need to create additional properties across various objects
- we will no longer need to create workflows to copy a value across objects. I.e. If property X gets updated at contact level, the value would be the same at Company level without having the need to create a workflow
- most of the time contacts/companies/deals can't be easily re-enrolled. This means as the value is updated in one object it doesn't always get updated across all objects automatically
- this will also be helpful from a reporting perpective as it would allow us to create more single object reports/dashboards
Yes this would save a LOT of time. ATM I have clients who need a handfull of properties that are exactly the same across multiple object E.g. BRAND.
We arre currently creating automaions to make sure if one is edited then they all get updated etc. But it is very frustrationg having to create the exact same property across 3-4 objects and then create workflows to match. it would be great too have this option even if it is only needed for 3-5 properties a client!
YES I agree and have asked for this! I would like to be able to see the same properties in my deals view that I see in contact view. I would like to attach the tme zone to each view along with other properties.
It makes for an easy read instead of wassting time searching in the profile
I couldn't agree more, adding properties across deals/companies etc indivually is redundant ...but judging by the fact this thread is nearly 3 years old and the issue hasn't been resolved.. not feeling confident that the customer support rep I spoke to today that said "I recommend that you vote and leave a comment on this idea. HubSpot’s product managers regularly review new ideas and engage with customers for their feedback. They'll put every effort into implementing ideas that will benefit the majority of HubSpot's user base and fit in within our product roadmap." really, every effort? Yet the issue is still unresolved. Clearly this would improve productivity of the app, please implement a solution!!!
This is messed up in HubSpot Creating multiple workflows just to copy paste properties across objects. Makes everything so much more complicated than need to be. Having this feature would drastically improve many features:
This is a HUGE need! Because HubSpot currently doesn't allow us to use cross-object personalization tokens in certain aspects of tasks, workflows, etc., we are constantly having to duplicate properties across objects in order to get the data we have into the hands of the right people.
Additionally, when we create a property with defined options (multi-checkbox, dropdown, etc.) that needs to be recreated across objects, we have to manually update every iteration of that property whenever a slight change needs to be made. This turns the 30 seconds it takes to add a choice into a 5 minute endeavor because we have to cycle through all of the objects with the identical property and manually update each of those, as well. And if we forget to do it to one or multiple, it can drastically screw up workflows that rely on that information being the same across objects.
Yes please, not having is a major drawback. Often leading to duplicate properties being created and silos between different objects if WF not set up correctly.
Absolutely needed. Current workaround of copying properties across objects is just bad database design (aka database denormalization).
Leads to update anomalies if the workflow doesn't work or is only one-way. If workflow is 2-way, can cause loops.
BTW Salesforce solves for this using Lookup fields. Basically instead of 'copying by value' it just shows the value 'by reference' from the related object.
This would also solve the use case of needing Company or Contact records to be updated at certain stages in a Deal pipeline. For example, when a Deal reaches X stage, we must ensure that the associated Company record has X value updated to function for our integration. If we had cross-object fields, we could make this required easily.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.