I would love to be able to add in the new association labels using a workflow - rather than needing to do this manually.
this would enable businesses who have contact A who makes a booking and Contacts B, C, D etc who attend a course or an event flagged as attendees. so a business knows which are valuable contacts.
It would also be helpful to be able to use a workflow to send different communications to clients based on their association tag.
@DStaat thanks for sharing. Found it somewhat surprising to read that Hubspot Ventures invested in your company Hapily. Seems like a bit of a conflict of interest in a way. It means if Hubspot solves these issues directly by allocating development time to them then you lose money - and they lose money indirectly through that. So then hubspot expects customers to pay for solutions made by a third-party to shortcomings 🤔
@MatthewBoyd I just noticed your reply concerning Integration Glue. I think I'm going to attempt to get a full demo. We're using another 3rd party app in our portal now called Associ8 that does the full functionality of what everyone here is talking about. However, it does seem to bog down when trying to do many associations in a single day. The associations can take beyond 60 minutes to complete through a workflow, and sometimes they don't work. I've had to create loops of workflows with exit triggers in order to get associ8 to function in the way that I need it to.
@SFoltz88 Hi there! I'm David from the hapily support team. We're the ones who created Associ8! I'm sorry to hear you're having troube using the app. If you'd like some assistance I'd be happy to help!
@zeke curious if you have any updates on this? I promise I am being patient and I am a product leader so I get it.
Without the abililty to set label associations (AND previously without the ability to grab data from associated objects as we now can in the Data Panel - Yay! ) ,we had to accomplish what we needed with Custom Code created for many thousands of dollars with a Certified Partner. Even so it turns out there are errors in that code and its very finicky and causes confusion and extra steps from our team members. I am facing a choice of spending many monies to have it redone before the teams revolt but if its truly on its way in this data panel I can wait.
Just because i know product teams like use cases:
- when we win a new deal we create a custom object record that we call a contract which contains a number of data elements telling us about the structure of that customer's agreement with us
- subsequent renewal and upsell deals need to ingest those data elements to provide proper deal and quote handling
- those subsequent renewals or upsells can result in a contract change, so we may end up with more than one contract record per company but only one of those is marked (via custom field) as active at a given time and this is done via workflow.
- so when a new upsell or renewal deal is created, we need to copy in the values from the current ACTIVE contract
- I see in the new data panel that we can filter to the last created or the last modified, and this will probably be correct 90% of the time but I can see where a backfill/mass-update or other scenarios mean those activity-based filters could be incorrect
- since this is some legal handling here, we can't tolerate that potential error. but if my workflow creating that contract record can instead set as "active agreement" assoication label all would be well. Thank you for listening!
As it so happens, today was going to be the day I gave an update as we've made some major breakthroughs recently that we wanted to share with everyone.
The new Data Panel beta feature is currently going through the final weeks of "beta testing" and will soon be available to all customers. We had a rather tricky setback this past month that took our entire team time to sort out but as of this week we've sorted out all the kinks and are back to working on the followup functionality needed for a "Set Association Label" action. While I can't give an estimate (for fear of hitting another setback and dissapointing people), I can say we have a much more clear line of sight to our goal and have many engineers actively working on the solution.
The good news is that this next milestone will include more than just the Association Label action. We are going to have the ability to support more field types and provide finer granularity on the types of records/data that can be pulled into a Workflow.
@zeke are there changelogs of updates/fixes to Beta features available?
I've been enrolled in the Data Panel beta for a few weeks now. I definitely wasn't able to leverage it the way I wanted, but perhaps that was related to some of the kinks you've sorted out.
Now I would assume you're not the one to bother... but it'd be a perfect time to roll out the aiblity to have more than 10 association labels per object as well (20 or so would be great).
I have a feeling this tool is going to litterally superchage the use of association labels.
@RyGuy the changes we're working through are towards the next set of features I'm referencing, for example, the Set Association Label action. Therefore there wouldn't be much if anything changed to the existing beta functionality. Definitely feel free to message me with details if you'd like.
@jaybaum I just met with our Associations team and discussed that hard limit. No hard decisions were made but we would like to fix that as well and could see traction in the coming months. I would recommend opening an idea on our forum so we can track progress, otherwise we'll hopefully have good news down the line
But our issue is that when you change association label (for example of a contact in a deal) then it doesn't update the modified date on either the deal or contact record. From my perspective, if you change the association label of a contact on a deal - it should at least change the last modified date on the deal record (i'd say also the contact). I see it as a 'shared' property - relevant to both. If you first associate a contact to a deal or company it also updates the last modified date on that record.
I wanted to use last modified as trigger for a workflow.
@Roeland_RS this sounds very much like a self resolving issue. Once setting association labels from workflows are added, it is highly likely they will enable it as a workflow trigger. If you must use "last modified date" as a trigger to the workflow, then perhaps just have a workflow triggering off of "Association Label" is Known and set a number property to increase or decrease by 1 as a solution.
But of course, we still have to wait for setting association labels to be available in workflows at all.
I'm assuming this ability to set association labels will apply to contacts>deals as well as contacts>tickets and other associations? Most of our customer interactions / deal generation occurs through the submission of forms, as do tickets, so we often end up with quadruplicate deals / tickets which we have to spend a huge amount of time merging to ensure our conversion data is accurate
I've tried all ways possible via custom properties but cannot square off unless we can have association labels set in contact based workflows so we can segment and identify one deal / ticket from another iwthin the contact based workflow. Any idea when the beta product will be released?
I expected the feature to work for associated labels, that if you associated a contact, it would be the same across all deals that the contact was associated with. I.e in my case - a shipping contact for the deal to be shipped to. Dealing with a partner / reseller network this is the same for most deals that one company orders and the manual associatoin is tedius to say the least.
Totally agree - I need to find a way to copy company properties to "New Deals ONLY" and remove the manual steps for the sales and customer success teams. I can't have all deals updated as this has a massive impact on the integrity of closed won deals. This would help solve that
