Beast Mode returning greater than 100% for Performance KPI
To keep it as short as possible, I have an On-Time delivery KPI. However, I have to measure on-time/late from two different columns depending on the type of delivery it was. I'm using this beast mode formula to capture those criteria, and then just simply divide it by the total number of deliveries:
(sum(case when `mode`='FTL' and `stop type`='Drop' and `on time / late (2 hrs)`='On Time' and `route category`= 'Transfer' then 1 else 0 end)+sum(case when `mode`='FTL' and `stop type`='Drop' and `on time / late`='On Time' and `route category`<>'Transfer' then 1 else 0 end))/count(case when `mode`='FTL' and `stop type`='Drop' then `route` end)
This formula keeps resulting in % that are over 100%. My first thought was an order of operations, but changing the formula either results in the same answers or something that is less than 1%.
I'll also note that when I take out the count denominator, I get the accurate number of on time deliveries between the two criteria, which makes me believe the denominator or the formula is the issue. Anyone ever have this issue?
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 753 Beast Mode
- 61 App Studio
- 41 Variables
- 692 Automate
- 177 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive