Time zones best practices management for daylight savings change

Reply
White Belt

Time zones best practices management for daylight savings change

Hello,

 

I have an issue regarding time zones management in Domo specifically for scheduling dataflows. If I'm right, we cannot change the time zone, that will always stay as UTC. I work in a country where we still have daylight saving time changes (France). Two weeks ago, a time change occurs and all my dataflows ran 1 hour too late and they are still running 1 hour too late cause I can't change all my dataflows each 6 months Smiley Wink

How did you manage once for all this daylight savings change in Domo or what the best way to fix it definitively ?

 

An other question, the Time zone change in Admin / Company Settings / Company overview is just for layout purpose ?

 

Thank you in advance for your help,

 

Philippe.


Accepted Solutions
Major Brown Belt

Re: Time zones best practices management for daylight savings change

My workaround is to run them more frequently. Unless the etl is doing something that will impact the result if run every hour, it should be a non-issue. It's a waste of back end Domo resources, but if it concerns them, they can work on a functionality for us to schedule based on our local time zones, and have their systems do the conversion on the back end.

In case it helps your sanity...I believe the reason it's all in UTC is to maintain alignment across global offices all on the same instance. This is excellent when you have a global team, but confusing as anything if your team is all in the same time zone.

Would be ideal for everyone to see everything in their time zone ID by ID, but I guess that gets really complicated.

Oh...I also recall that it would cause issues with things like the Salesforce connector and the date/time stamps imported as data. I don't recall the specifics, but when it was explained to me years ago, it sounded like it would be a nightmare to work out.
DataMaven
Breaking Down Silos - Building Bridges
Check out my story!
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"

All Replies
Highlighted
White Belt

Re: Time zones best practices management for daylight savings change

Sorry, I forget, I have this issue with dataflows and also Domo native connectors (as Jira for example).

 

Regards,

 

Philippe.

Major Brown Belt

Re: Time zones best practices management for daylight savings change

My workaround is to run them more frequently. Unless the etl is doing something that will impact the result if run every hour, it should be a non-issue. It's a waste of back end Domo resources, but if it concerns them, they can work on a functionality for us to schedule based on our local time zones, and have their systems do the conversion on the back end.

In case it helps your sanity...I believe the reason it's all in UTC is to maintain alignment across global offices all on the same instance. This is excellent when you have a global team, but confusing as anything if your team is all in the same time zone.

Would be ideal for everyone to see everything in their time zone ID by ID, but I guess that gets really complicated.

Oh...I also recall that it would cause issues with things like the Salesforce connector and the date/time stamps imported as data. I don't recall the specifics, but when it was explained to me years ago, it sounded like it would be a nightmare to work out.
DataMaven
Breaking Down Silos - Building Bridges
Check out my story!
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"
Announcements
Looking for the latest Dojo Community solutions? Click on the "NEW SOLUTIONS' widget title or go to https://dojo.domo.com/solutions Click here!