Result of Date functions do not align in Transform
I am getting the wrong date listed when I use CURRENT_DATE() in a transform and it is a causing my data to display incorrectly. Why does it show the date at Dec 7 when it was actually Dec 6 as the NOW() function shows?
How do I fix this?
Comments
-
This issue MAY have to do with your company's time zone settings that admins can set. I know that beast mode functions are affected by this.
Check out this link for more info, it might provide a possible solution: https://knowledge.domo.com/?cid=timezoneissues
Specifically, potentially using the MySQL function "CONVERT_TZ()" to convert into your relevant time zone.
0 -
Unfortunately, I have tried convert_tz and our admin setting are set with our timezone correctly.
0 -
Hm, well if there are differences between the two functions only at certain times of the day, like starting later in the afternoon, then I would say that it is a time zone issue, otherwise I would open a ticket with DomoSupport since that shouldn't be happening.
0 -
I actually found a solution. In beastmode (because the timestamps are correct in the transform) I used convert_tz(`date`,'us/eastern','us/eastern'). This corrected the timestamps and properly took into consideration daylight savings.
1
Categories
- All Categories
- 1.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 278 Workbench
- 4 Cloud Amplifier
- 4 Federated
- 2.7K Transform
- 89 SQL DataFlows
- 557 Datasets
- 2K Magic ETL
- 3.3K Visualize
- 2.3K Charting
- 571 Beast Mode
- 11 App Studio
- 28 Variables
- 579 Automate
- 141 Apps
- 414 APIs & Domo Developer
- 23 Workflows
- 1 DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 352 Distribute
- 92 Domo Everywhere
- 258 Scheduled Reports
- 2 Software Integrations
- 92 Manage
- 89 Governance & Security
- 9 Product Release Questions
- Community Forums
- 42 Getting Started
- 28 Community Member Introductions
- 88 Community Announcements
- 4.8K Archive