How can I prevent a running backlog total beastmode from hitting zero?
I'm working on building a labor model for my department to track where our projected backlog will be over the next several weeks. One problem I'm running into is when the incoming backlog is less that what we're projected to process, the backlog goes into the negative instead of hitting zero which then throws off all subsequent projections. Any idea on how to rewrite this so that the total will never drop beyond 0?
Below is a simplified version of the beastmode I currently have written
/*current total backlog*/
SUM(SUM(`backlog per unit`)) OVER()
+
/*Incoming/Projected backlog Beastmode*/
SUM(SUM(`incoming backlog`)) OVER (ORDER BY `week starting`)
-
SUM(SUM(`units processed`)) OVER (ORDER BY `week starting`)
Answers
-
@TylerMarshall How is your data grouped in the card? You many need to add a PARTITION BY and/or ROWS clause in your window functions
0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 302 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 104 SQL DataFlows
- 637 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 761 Beast Mode
- 65 App Studio
- 42 Variables
- 704 Automate
- 182 Apps
- 458 APIs & Domo Developer
- 53 Workflows
- 11 DomoAI
- 39 Predict
- 16 Jupyter Workspaces
- 23 R & Python Tiles
- 401 Distribute
- 116 Domo Everywhere
- 277 Scheduled Reports
- 8 Software Integrations
- 132 Manage
- 129 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 111 Community Announcements
- 4.8K Archive