Beastmode Timediff Errors
Hi all, using the following to calculate time differences between requested and actual drop off times:
TIME_TO_SEC(TIMEDIFF(Actual Drop-off Time
,Requested Drop-off Time
)) / 60
Seems like the math isn't panning out (first column should be ~25 in the time difference column but instead is showing 1415.80). Haven't used the timediff function before in Domo, so any advice on how to modify my beastmode formula to reflect the time difference in minutes between these two timestamp columns would be much appreciated.
Best Answer
-
For differences in time this is my preferred approach
(UNIX_TIMESTAMP(new_timestamp) - UNIX_TIMESTAMP(old_timestamp))
You can then divide the result to get to the grain (day,hour,min,seconds) you want to.
David Cunningham
** Was this post helpful? Click Agree 😀, Like 👍️, or Awesome ❤️ below **
** Did this solve your problem? Accept it as a solution! ✔️**0
Answers
-
For differences in time this is my preferred approach
(UNIX_TIMESTAMP(new_timestamp) - UNIX_TIMESTAMP(old_timestamp))
You can then divide the result to get to the grain (day,hour,min,seconds) you want to.
David Cunningham
** Was this post helpful? Click Agree 😀, Like 👍️, or Awesome ❤️ below **
** Did this solve your problem? Accept it as a solution! ✔️**0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 307 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 112 SQL DataFlows
- 649 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 790 Beast Mode
- 78 App Studio
- 43 Variables
- 746 Automate
- 187 Apps
- 475 APIs & Domo Developer
- 68 Workflows
- 16 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 406 Distribute
- 117 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 139 Manage
- 136 Governance & Security
- 8 Domo Community Gallery
- 47 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive