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.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 278 Workbench
- 4 Cloud Amplifier
- 4 Federated
- 2.7K Transform
- 89 SQL DataFlows
- 556 Datasets
- 2K Magic ETL
- 3.3K Visualize
- 2.3K Charting
- 569 Beast Mode
- 11 App Studio
- 27 Variables
- 578 Automate
- 140 Apps
- 414 APIs & Domo Developer
- 23 Workflows
- 1 DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 351 Distribute
- 91 Domo Everywhere
- 258 Scheduled Reports
- 2 Software Integrations
- 92 Manage
- 89 Governance & Security
- 9 Product Release Questions
- Community Forums
- 42 Getting Started
- 28 Community Member Introductions
- 85 Community Announcements
- 4.8K Archive