Nov 30, 20203:21 AM - edited Nov 30, 20203:31 AM
HubSpot Employee
How to create a 'Today's date' date property.
SOLVE
I recently discovered this smart way to create and maintain a 'Today's date' property using workflows. This can then be used in reporting, workflows and lists.
To do this you can follow these steps: 1) Create a custom date field property
2) Create a contact-based workflow with the enrollment triggers 'Today's date is known' OR 'Today's date in unknown'. 3) Turn on re-enrollment for 'Today's date is known'. 4) Add an if/then branch action with the trigger 'Today's date is known'. 5) After the NO branch add the action 'set property value' and then set 'Today's date' to the 'date of step'. 6) After the YES branch add the the action 'set property value' and then set 'Today's date' to the 'date of step'. 7) The last steps after the YES branch will be a delay. To do this you will chose 'delay until a day or time' and then choose 00:15 or any other time after midnight.
This workflow will then work in the backround to always make sure each contact has today's date saved as the value on their record. The same can be repeated for company and deal properties.
It really is so crazy that “Today’s Date” isn’t a native value available globally in HubSpot. The workflow outlined in this post is a great workaround though. I recorded a quick video of setting it up, which hopefully is helpful to folks.
I am not sure why it needs to be so complicated. I found a solution that simply changes the date if it is not known or is over a day old. It would be nice if HubSpot simply fixed the issue by providing an option to select todays date (rolling).
There is a new option in Workflows for a SCHEDULED workflow option. If you have the ability to set up a scheduled workflow option here is what the setup should look like now for an EASY Today's Date property for any object.
Really appreciate you going to the trouble of finding this workaround, but it is kind of unbelievable for a CRM of HubSpot's size and prestige to not offer relative date values!
Reposting this relevant master idea that addresses this issue to upvote for others who are struggling:
Sep 28, 20214:20 AM - edited Sep 28, 20215:51 AM
Top Contributor
How to create a 'Today's date' date property.
SOLVE
Thanks everyone for a great solution to a problem that shouldn't exist! HubSpot, please make it so!
Ah, and I noted that if you calculate the date using the between function, it returns a positive integer regardless of whether the close date is in the past.
You can get around that by using an additional property set by a workflow that I call 'PastDate' which after 'Today's Date' is set, checks to see if the property 'close date' was in the past and sets this to true. Then you add a condition to the property (here: Days to close from today') so that it will only be calculated if PastDate is false.
Workflow:
Days to close from today property settings:
And yes, this makes this iterative (since PastDate is generated via a workflow that only runs once a day, basically, this value will lag by one day), but I can live with that rather than having deals show up with values in multiple years because they were closed far in the past...
Hi folks, I have actually tried this and found that it is not possible to keep updating the custom "Today's Date" property through a workflow as it would not keep updating the property through an endless loop automatically.
If you're testing this on your portals, you might want to keep manually re-enrolling your deals to keep the "today's date" property updated.
I sent a direct request to VP of Global Customer Support (David Hunt) on October 14th, 2020 -- still no word, no progress.
What can the community do to push Hubspot decision makers to prioritize a 2-week sprint for a dev team to add this feature?
Or maybe they ignore this feature because a Hubspot employee said there is a workaround and we don't need the feature?
There should be a fulltime dev team making enhancements, and prioritizing "must-have" features, and this feature should have been lifted to the top of priorities last year (or actually, this feature should have been built into the original version1, out of the box).
Because we don't have this feature, I've given up on Hubspot and do 90% of reporting outside of Hubspot. The charting tools are weak, Hubspot doesn't have a web-based SQL editor to query on HS data (which would solve the today's date problem with getdate() and datediff functions), and it doesn't have must-have features like Today's Date. Customer support is excellent, but even when they made these workflows for us, it broke and gave incorrect data. The workaround workflows is not a suitable solution.
@PamCotton@OliviaB Tell whoever prioritizes the dev team for enhancements to call me, and I will explain face to face if need be. Or come and try your best workflows in our system and give us a Today's Date without it blowing up. Customer Support couldn't do it. It worked for 1 day and then broke, giving wrong data.
Hello @bi_developer, thank you for your feedback, I would like to apologize for the frustrations, data issues, and business impact this has caused.
At the moment our best recommendation is to please leave your feedback on the idea you specifically share, Upvoting in that idea will specifically alert our Product Team to the popularity of this request. Doing so will also auto-notify you if/when this functionality becomes available within HubSpot. You may read more about how that review process works here.
Hi Pam, regardsing your recommendation to @bi_developer "leave your feedback on the idea you specifically share, Upvoting in that idea will specifically alert our Product Team to the popularity of this request. " Haven't they already don that here? And I understand the concept of counting upvotes to determine interest but there are so many legs to the same topic just counting upvotes to one particular post total underestimates the criticality of resolving this issue.
From what I've read customers have been posting for years, not weeks or even months, requesting a solution to this issue yet the best answer is to post more requests and wait? Even a letter to the VP of Customer Service received no response! Maybe if HubSpot shared an active list of issues they arecurrently working on solving that is more important than this we'd be a little more patient. I am a new customer to HubSpot and am seriously questioning the decision to continue with this CRM, therefore, I'm sure others are too. Please give us confidence we made the right decision by not only listening to our concerns but promptly resolving them.
@OliviaB Are there any updates from the Hubspot side? Seems like everyone is having to use tools outside of HubSpot or game the system to get a simple requirement so we can use calculated properties effectively or use for BI reporting. Any updates would be great.
Ok, so I'm not the only one who thinks it's a little crazy that we can't use something like 'Today'
Has anyone from HubSpot confirmed why these contacts are not enrolling? I have built out mine with delays, seems like it should work, but I'll need to wait on the schedule to confirm.
It's essentially the same as the original solution by Olivia. Difference is I do the delay in the Yes branch before executing the step to 'set property value' to 'date of the step'.
My workflow starts after Midnight and will enroll all the contacts. (We have 5k-6k currently, should stay under 10k for quite sometime) The Unknown branch will set the date immediately, the Yes branch will give it an hour delay befor hitting all of those. It will re-enroll if the Date is Known, but won't re-enroll if unknown. In reality, no contact that ever re-enrolls will ever have a blank value.
Here is my solution to a date stamp for Today's Date in Deals, similar to the solution by @helenasolsona :
It works well for Deals, but we only have hundreds, not millions.
It would really help to have a Today's date option built in to the Time Between date calculation properties so we don't have to use a workaround like this.
I'm hoping HubSpot can make the date calculation options much more robust soon.