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
Best Answer
-
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
**Say "Thanks" by clicking a reaction in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1
Answers
-
Sorry, I forget, I have this issue with dataflows and also Domo native connectors (as Jira for example).
Regards,
Philippe.
0 -
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
**Say "Thanks" by clicking a reaction in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1 -
Our issue is with workbench scheduled jobs: local time is Pacific, but workbench is saving jobs in UTC.
Workbench scheduled jobs automatically change to +1 in March and -1 in November, changing schedule to an incorrect time.
We were hoping changing the Company Settings time zone from UTC to local time would resolve the issue, but it didn't. I'm assuming this means the scheduled time is associated with Domo's system, and not our company instance.
It appears there still isn't "functionality for us to schedule based on our local time zones", as mentioned by @DataMaven.
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 296 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 614 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 729 Beast Mode
- 53 App Studio
- 40 Variables
- 677 Automate
- 173 Apps
- 451 APIs & Domo Developer
- 45 Workflows
- 8 DomoAI
- 34 Predict
- 14 Jupyter Workspaces
- 20 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 121 Manage
- 118 Governance & Security
- Domo Community Gallery
- 32 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive