Cards displaying today when set to yesterday - possible time zone setting issue

Jbrorby · December 2023

Our local time here is 6 hours behind UTC. We have a card that is set to display "yesterday" and it is a datetime column. I checked the card at 5:55 PM and it was displaying [yesterday's] data, then I checked it again at 6:01 PM and it was displaying [today's] data. So it seems like the "yesterday" in the card calendar section is based on UTC instead of our time.

In the domo admin section, our company setting is set to UTC. This is done with the assumption that Domo expects the data coming in to be in UTC, and since the data coming in is in our local time, we wouldn't want Domo to subtract 6 hours from the data coming in if we set our company setting to central. Does this sound correct?

My personal profile and the card creators personal profile are set to central/chicago

Does anyone have any thoughts on this?

DashboardDude · December 2023

Hi @Jbrorby ,

So the timezone in Admin is different from the timezone used to pull in data. Go ahead and change the admin timezone to central.

As for datasets, you can change that in scheduling and while the displayed default is in UTC, you'll see CST right next to it so I just put all my dataset updates in CST.

Made a video for you:

https://www.loom.com/share/59b6b10b019e4d778a962245213ae3d7?sid=23cfd467-7283-408a-9d2d-3c6e1b203cfb

Let me know if that helps

GrantSmith · December 2023

To clarify, the company timezone is what the UI will display your timestamps with and will convert the values when the data is displayed. Domo assumes UTC for all data being imported.

DashboardDude · December 2023