Timezone Settings - Need Assistance
**Be sure to select the answer that represents the best solution and mark as "Accept as Solution"
Best Answer
-
Tyler -
While I have not implemented the changes yet due to some necessary coordination, here's what I have learned, and hopefully you will find this helpful.
If your date fields have a DATE datatype, then you shouldn't have an issue. But if your date fields are of a DATETIME datatype, then read on...
If you are loading data through Workbench, there is a hyperlink for Job Configuration. In the corresponding pop-up, you can set the timezone that represents the basis for your data (probably wherever your servers are located). By doing so, DOMO translates your records' timestamp FROM wherever they are recorded (lets use US Central time as an example), and adds +6 Hours to convert the result TO UTC (which for our purposes, and given the clock adjustment, is effectively moving it to Greenwhich Mean Time, or the equivalent +/-0 Hours time).
THEN, in the Domo Admin Company Settings page, set your Company Timezone to match wherever your data came from - in my example, US Central Time. So, what does all that do for you? Workbench/Job Configuration adds X hours to your timestamps; Domo Admin Company Settings subtracts those same X hours. Net zero impact, right? But not really... now Domo knows where your data is based, and supposedly can now manage your "Yesterday" based on YOUR timezone. What happened if you left everything at UTC is that as soon as your "yesterday" records became 24 hours older (by timestamp) than GMT, they started to evaporate from your Domo card results.
Again, keep in mind... this is all based on feedback and guidance I received from DomoSupport - I have not yet implemented this on my side, but the approach makes sense. If you get a chance to try it before I do, please post back how it worked for you!
**Say thank you by clicking the 'thumbs up'
**Be sure to select the answer that represents the best solution and mark as "Accept as Solution"6
Answers
-
ckatzman, were you able to get some help with this? I face the same issue and it makes things very difficult to use the 'yesterday' results.
I'd also be interested to know how you came up with Business Days in Domo. I tried a few approached but ended up creating business days in Excel and then loaded it to Domo.
0 -
Tyler -
While I have not implemented the changes yet due to some necessary coordination, here's what I have learned, and hopefully you will find this helpful.
If your date fields have a DATE datatype, then you shouldn't have an issue. But if your date fields are of a DATETIME datatype, then read on...
If you are loading data through Workbench, there is a hyperlink for Job Configuration. In the corresponding pop-up, you can set the timezone that represents the basis for your data (probably wherever your servers are located). By doing so, DOMO translates your records' timestamp FROM wherever they are recorded (lets use US Central time as an example), and adds +6 Hours to convert the result TO UTC (which for our purposes, and given the clock adjustment, is effectively moving it to Greenwhich Mean Time, or the equivalent +/-0 Hours time).
THEN, in the Domo Admin Company Settings page, set your Company Timezone to match wherever your data came from - in my example, US Central Time. So, what does all that do for you? Workbench/Job Configuration adds X hours to your timestamps; Domo Admin Company Settings subtracts those same X hours. Net zero impact, right? But not really... now Domo knows where your data is based, and supposedly can now manage your "Yesterday" based on YOUR timezone. What happened if you left everything at UTC is that as soon as your "yesterday" records became 24 hours older (by timestamp) than GMT, they started to evaporate from your Domo card results.
Again, keep in mind... this is all based on feedback and guidance I received from DomoSupport - I have not yet implemented this on my side, but the approach makes sense. If you get a chance to try it before I do, please post back how it worked for you!
**Say thank you by clicking the 'thumbs up'
**Be sure to select the answer that represents the best solution and mark as "Accept as Solution"6 -
Thank you for these posts. I would love Domo to add a "just don't mess with my timestamps, ok?" button.
We have restaurants across the country and the POS records everything in local time. As far as I'm concerned, local time is what I want. If I want to see how busy we are between 11 and 1 I want everyone's local 11 and 1. And since all that data comes into one SQL server, it would be a nightmare to even think about tweaking what comes in.
I am currently re-uploading ~ 40 million records that I have now set to our corporate timezone which is what I have set in Domo so hopefully this does the trick.
0 -
SeanPT,
Feel free to propose your idea in our ideas exchange here. It will then get reviewed by product management and can be voted up by clicking on the white arrow by your fellow Dojo members.
Thanks in advance!
Dani
0 -
Hey Guys - The timezone issues are plentiful, and are consistently in the ideas exchange.
If I don't already have one in there, it's on my list of things to add. I had to eat some serious crow when I realized a Salesforce report I had scheduled to run on the first of each month, with criteria of 'prior month' ran on UTC. This meant that it ran at like 8PM on the last day of the month, and thus pulled 2 months prior. It was a new project showcasing how swanky Domo was, and let's just say it wasn't my favorite learning experience!
Here are the results on Ideas Exchange:
And here's the search pop-up in Dojo, in general:
We all definitely need better time zone handling. Anything scheduled should have a drop-down for time zone. If Domo needs to convert THAT to UTC to normalize and make things happen at the right time, that's fine, but it should not be something the users need to contend with. Likewise, times in our datasets should not be messed with, unless specified.
This is definitely a hot topic that many Domo users are struggling to work around. I'm sure it's tough to solve on the back end, or Domo would have taken care of it by now. But perhaps that little something extra is needed to bring it to the finish line.
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"0 -
WOW - and I just saw the dates on this! I don't know why Dojo showed it as a recommended thread in the sidebar for me!
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"0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 295 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 608 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 710 Beast Mode
- 49 App Studio
- 39 Variables
- 667 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 44 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 115 Manage
- 112 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive