May 24, 2022 8:30 AM - edited May 30, 2022 9:00 AM
The Operations Hub Show & Tell is back!
Tomorrow, May 25 at 10, our product team will talk about Operations Hub, what it is, and how they're thinking about its future.
Joining us will be Frans Leys (Data Sync), Megan Legge & Zach Webert (Automation), and Stephen McMillian (Datasets).
Please use this thread if you have any questions for these speakers regarding Operations Hub and its features!
Some additional resources:
May 27, 2022 11:22 AM
Great showcase guys!
On the formatting data side of things, there are some use cases where we need to generate new values instead of working with what is available. Currently, custom code actions are an overly complicated way to do the following:
I'm also starting to see the need from teams to evenly distribute leads and record ownership based on who has the least records assigned to them. Ex: Agent 1 has 20 tickets, Agent 2 has 5 tickets. Assign the next 15 to Agent 2 or until they are even. The limits found in Hubspot workflows is that Hubspot user data can't be surfaced anywhere, turning users into a Hubspot object would be a great way to surface this data.
Jul 21, 2022 4:24 PM
Hi @Hawk-Steve ,
We recently added a random number generator formula to "custom mode" in format data action:
I'd love to hear your feedback and questions if you, or anyone else here, tries it out. Thanks for the input!
Jul 27, 2022 7:31 AM - edited Jul 27, 2022 7:55 AM
That's awesome @MeganLegge !
A recent task I'm onto is creating automated Credit IDs for customers who are due to receive credit. The credit ID must be unique and must be 6 characters long, e.g. A12345, B67890.
I wonder If I can generate a number using RNG, then use a custom code action to check if a duplicate exists against another record, if it does, repeat.
This came about with a CS team recently moving away from zendesk, where they used the 5-digit ticket ID that was generated. Adding Z to the start completed the 6-character requirement for a credit ID. In Hubspot this is not possible as ticket IDs are 9+ characters, hence why I need to generate this shorter UID for tickets.
EDIT: I also just noticed that it errors if I was to do something like this randomNumber(00001,99999). Ideally, I'd want to generate a number with a set number of characters.
Sep 7, 2022 9:25 AM
Hi @Hawk-Steve ,
The error is because the validation here is essentially interpreting "00001" as an incorrectly entered "1." To force a 5 digit result, enter randomNumber(10000,99999) instead. Hope that helps : )
Following up another one of your ideas above where you mention keeping only the first letter of a name, we've now added the ability to trim values using "Left" and "Right" formulas. Here's an example where you could take a long account number, and use just the last 4 digits:
Keep the ideas coming : D
Sep 14, 2022 6:24 AM
Mind blown @MeganLegge! Big thank you to you and the team behind these improvements, this is great!
Jun 28, 2022 8:51 AM - edited Jun 28, 2022 8:51 AM
Thanks for your feedback and ideas for formatting data, this is super helpful for us as we explore adding more formulas and functionality. We have an idea for an RNG (random number generator) and are currently doing development work to bring something like this to the Format Data action. I'll follow up here when there's more information to share.