topic Re: Format Date and Time: Daylight Savings v. Standard in Data Hub

Format Date and Time: Daylight Savings v. Standard

00000 — Mon, 28 Oct 2024 19:38:19 GMT

How can we reference the account's timezone in the timezone field when formating date and time through workflows?

Organization wants the time a property is changed to be stamped into a text property string so this information is visible for users on the property record. Each time it changes, the property string is updated.

However, using format date and time in the workflows seems to require a hard entry in the timezone field, like UTC-5, UTC-6. UTC-5 works for now, but in a couple weeks in the US UTC-6 will be needed.

Re: Format Date and Time: Daylight Savings v. Standard

BérangèreL — Tue, 29 Oct 2024 09:55:31 GMT

Hi @00000, I hope that you are well!

Great question, thanks for asking the Community!

I'd like to share this documentation that might be of interest: "How should timestamps be formatted for HubSpot's APIs?".

Also, I'd love to put you in touch with some of our Top Experts: Hi @HubSpot_Corey, @miljkovicmisa and @HFisher7 do you have suggestions to help @00000, please?

Thanks a lot and have a wonderful day!

Best,
Bérangère

Re: Format Date and Time: Daylight Savings v. Standard

miljkovicmisa — Tue, 29 Oct 2024 10:51:44 GMT

Hello @00000 ! Thank you for writing in the forum.

From what I can understand, you are trying to set a value to a property, and that value should be the time when a property changes.

This could be accomplished with the following steps:

1. Create a workflow that triggers when the property in question changes.
2. Create a new custom "date and time" property that will hold the date and time the property changed (see screenshot 1).
3. Add a step (set property value) to the workflow that sets a property value. When the property is a datetime property, like the one you created previously, it enables you to add the date and time of the step (see screenshot 2).
4. After the w/f runs you will get the datetime of the step (see screenshot 3).

Screenshot 1.

Screenshot 2.

Screenshot 3.

Should you need further assistance with this don't hesitate to ask.

Hope my answer helped you with your usecase, if so, please mark this answer as accepted 😉

Re: Format Date and Time: Daylight Savings v. Standard

00000 — Tue, 29 Oct 2024 13:27:56 GMT

Hi @miljkovicmisa ,

I am specifically asking about how to set the timezone format to the account's timezone. Screenshot below. Right now UTC-5 matches our timezone, but in a week daylight savings means the timezone will change to UTC-6. Is there a way to reference the primary timezone of the client through a token so this wouldn't need to be updated manually upon savings/standard switches? Perhaps you answered this question in your screenshots, but the links don't appear to be working.

Side note: A custom date-time property as every time this property changes it needs to be included in a list and visible, so a text string is needed instead. This portion of the workflow has been solved. I am specifically asking about the time zone formatting.

Re: Format Date and Time: Daylight Savings v. Standard

00000 — Tue, 29 Oct 2024 13:30:31 GMT

@miljkovicmisa, @BérangèreL

My inserted screenshot did not save correctly either. Trying again.

Re: Format Date and Time: Daylight Savings v. Standard

00000 — Tue, 29 Oct 2024 13:32:00 GMT

Try 3. I'd take a screenshot of the photo inserted in the post before hitting reply, but guess that wouldn't do much here.

Re: Format Date and Time: Daylight Savings v. Standard

00000 — Wed, 30 Oct 2024 14:53:20 GMT

Issue with screenshots solved- cannot see in Firefox browser and need to update my settings.

Re: Format Date and Time: Daylight Savings v. Standard

BérangèreL — Wed, 30 Oct 2024 16:23:30 GMT

Hi @00000, I hope that you are well!

Thank you for sharing the update about the screenshots and for sending them over!

I understand that you'd like to have a time zone token when you format the data via workflow so that you don't need to update it manually. Let me know if that's not the case.

I'd like to invite some of our Top Experts and Community Members to this discussion: Hi @miljkovicmisa, @HubSpot_Corey and @JGrandperret do you have a way to achieve this to help @00000, please?

Thank you very much and have a great day!

Best,
Bérangère

Re: Format Date and Time: Daylight Savings v. Standard

miljkovicmisa — Fri, 01 Nov 2024 08:06:11 GMT

Hello @00000 ,

After taking a closer look to the specific field, it seems that HubSpot automatically adjusts the timestamp according to the account's timezone when filtering and it converts the value for each user's timezone is used when viewing the property (see screenshot).

It is not clear to me what exactly you're trying to achieve, why is this property not correctly showing for you and your users, what it shows and what it should show.

Could you please be more specific and show us examples of your specific usecase?

Re: Format Date and Time: Daylight Savings v. Standard

00000 — Fri, 01 Nov 2024 14:02:05 GMT

@miljkovicmisa,

We are not using a datetime property to expose the time the original property changed because every previous time the original property changes needs to be stay exposed. Instead we are using a text string, so that the exposure property can continue to list the previous moments of changes. To do this, the moment of change is being formatted per the screenshot below and then the exposure property is being updated through concat([existing exposure property],", ",[format data output]).

As visible in the screenshot below, I have to type "UTC-5" or "UTC-6" to match the client's timezone hours. I was hoping to find a way to insert a dynamic token or custom code to avoid having to update the workflow manually each year since the exact dates of the spring forward/fall back shift each year.

Thanks,

Chel

Re: Format Date and Time: Daylight Savings v. Standard

BérangèreL — Thu, 19 Dec 2024 16:19:36 GMT

Hi @00000,

Thanks for the additional information!

For new feature suggestions, I'd recommend first to search and check if this idea is already present on our Ideas Forum here. If you find a similar idea, give it an upvote and share your unique use case in the comments.

If the idea doesn't exist already, please consider posting and creating a new Idea on our Ideas Forum here.

Thank you for being part of the discussion!

Best,
Bérangère