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.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 731 Beast Mode
- 55 App Studio
- 40 Variables
- 682 Automate
- 175 Apps
- 451 APIs & Domo Developer
- 46 Workflows
- 10 DomoAI
- 35 Predict
- 14 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 122 Manage
- 119 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 107 Community Announcements
- 4.8K Archive