Date format and timezone strike again (SSA)!

redvivi · 2024-09-13T16:16:15.375Z

Hey guys,

I need a second pair of eyes here.
I have a SSA calling a package returning :

{"value":"2024-09-24T20:45+10:00","timeZone":"Australia/Brisbane"}

I return therefore through a custom object the value* 2024-09-24T20:45+10:00 cast to Date type, and of course the timeZone as string which I expect to use as Dynamic Timezone.

So, back on front-end, I display this date (which comes as Sep 24, 2024 12:45 pm with dynamic timezone set to Australia/Sydney, which displays as Sep 24, 2024 10:45 pm. As I am displaying the original value with its original timezone, I would have simply expected the original value, e.g; Sep 24, 2024 08:45 pm (2024-09-24T20:45+10:00).

What am I missing?

PS: Yes, I could just return the date as a string, just wanted to make it fancier…

tylerboodman · 2024-09-13T17:50:28.108Z

When you return it through the date field I suspect it is incorporating the server environment’s time zone… could you use luxon - npm to incorporate the Australia/Sydney time zone before returning the date?

jonah.deleseleuc · 2024-09-13T20:45:49.191Z

Do you think using a Unix timestamp or an ISO with TZ +00 might make this easier?