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
- Product Ideas
- 2.1K Ideas Exchange
- Connect
- 1.3K Connectors
- 309 Workbench
- 7 Cloud Amplifier
- 10 Federated
- Transform
- 665 Datasets
- 120 SQL DataFlows
- 2.3K Magic ETL
- 827 Beast Mode
- Visualize
- 2.6K Charting
- 90 App Studio
- 46 Variables
- Automate
- 198 Apps
- 488 APIs & Domo Developer
- 97 Workflows
- 24 Code Engine
- AI and Machine Learning
- 23 AI Chat
- 4 AI Projects and Models
- 18 Jupyter Workspaces
- Distribute
- 119 Domo Everywhere
- 283 Scheduled Reports
- 11 Software Integrations
- Manage
- 145 Governance & Security
- 13 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 116 Community Announcements
- 5K Archive