CURRENT_DATE reflective of instance time zone

user11564
Member
Requesting CURRENT_DATE function in beastmode to be reflective of our company time zone instead of UTC. At 6pm daily (Central Time), our reporting is off as the UTC current date shifts to the next day. We were originally told this was a bug but after four months waiting for the fix, Support has come back saying this is functioning as intended. They are recommending we update all of our beastmodes (over 100 using this formula) to: DATE_ADD(CURRENT_DATE(), INTERVAL -5 HOUR) However, this does not take daylight savings time shifts into consideration. Requesting feature update to make CURRENT_DATE reflective of our company time settings.
Tagged:
1
Categories
- All Categories
- Product Ideas
- 2.1K Ideas Exchange
- Connect
- 1.3K Connectors
- 309 Workbench
- 7 Cloud Amplifier
- 10 Federated
- Transform
- 663 Datasets
- 119 SQL DataFlows
- 2.3K Magic ETL
- 823 Beast Mode
- Visualize
- 2.6K Charting
- 86 App Studio
- 46 Variables
- Automate
- 193 Apps
- 483 APIs & Domo Developer
- 87 Workflows
- 23 Code Engine
- AI and Machine Learning
- 23 AI Chat
- 4 AI Projects and Models
- 18 Jupyter Workspaces
- Distribute
- 117 Domo Everywhere
- 283 Scheduled Reports
- 11 Software Integrations
- Manage
- 143 Governance & Security
- 11 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 116 Community Announcements
- 5K Archive