CURRENT_DATE reflective of instance time zone
Options

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
- Data Connections
- 1.3K Connectors
- 309 Workbench
- 17 Cloud Integrations
- Data & ETL
- 2.3K Magic ETL
- 120 SQL DataFlows
- 667 Datasets
- Visualize & Apps
- 90 App Studio
- 198 Pro-code Components
- 2.6K Charting & Analyzer
- 873 Calculations & Variables (Beast Mode)
- AI & Data science
- 23 Domo AI & AI Chat
- 4 Managing AI
- 18 Jupyter Workspaces
- Automate
- 122 Workflows
- Alerts
- Distribute
- 118 Domo Everywhere
- 284 Reporting
- Manage
- 146 Governance & Security
- 489 APIs
- 11 Add-ins & Plugins
- 13 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 118 Community Announcements
- 5K Archive