Beast Mode Case Statement Help
For some reason this CASE statement will not validate. I have all the required parts. `PayTotal` and `PayTargetWeek` are both number values and I want this field to return a character string.
case when (sum(`PayTotal`) / `PayTargetWeek`) <= .05 then 'Under Target'
when (sum(`PayTotal`) / `PayTargetWeek`) >= .049 and <= .05 then 'On Target'
when (sum(`PayTotal`) / `PayTargetWeek`) >= .051 then 'Above Target'
else 'Not Sure'
end
Data Analyst
Bolt Express
Best Answers

I also tried writing it this way but again...it will *not* resolve/validate.
case when (sum(`PayTotal`) / (CASE when `PayTargetWeek` = 0 then 1 end)) <= .05 then 'Under Target'
when (sum(`PayTotal`) / (CASE when `PayTargetWeek` = 0 then 1 end)) >= .049 and <= .05 then 'On Target'
when (sum(`PayTotal`) / (CASE when `PayTargetWeek` = 0 then 1 end)) >= .051 then 'Above Target'
else 'Not Sure'
endChad Bishop
Data Analyst
Bolt Express0 
Hi Chad
Generally speaking, beast modes with aggregations within case statements are pretty tricky.
Why are you summing PayTotal but not aggregating PayTargetWeek? What your beast mode is doing is adding up a bunch of rows to get the sum of PayTotal, but then comparing the aggregation against a single row's PayTargetWeek value. Comparing aggregates against single rows does not usually work like you want or expect. Is PayTargetWeek the same value for every row that PayTotal is being summed on? Like, a single row of data has an individual PayTotal for a day or person or something but then it also has a wider PayTargetWeek value, that's not the same granularity? You can get around that by averaging your PayTargetWeek value in the denominator (assuming different granularities)
Also, you are missing something in your second comparison. Each comparison needs two values. Your "<= .05" comparison lacks the first value. The aggregation can't carry over. You'll have to compute that aggregation fully in each comparison.
In addition, there might be values between .05 and .049, or .05 and .051, so your would need to adjust the operators to leave no gaps. This won't make your beast mode validate, but it makes the results more usable.
Try this and see what happens:
case
when sum(`PayTotal`) / AVG(`PayTargetWeek`) <= .05 then 'Under Target'
when sum(`PayTotal`) / AVG(`PayTargetWeek`) > .05 and sum(`PayTotal`) / AVG(`PayTargetWeek`) <= .05 then 'On Target'
when sum(`PayTotal`) / AVG(`PayTargetWeek`) > .05 then 'Above Target'
else 'Not Sure'
endAaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 
By the time I opened this thread, SUM(`PayTotal`) was just a troubleshootingitteration of the case() statement I was trying to make work.
I took your suggestion and modified it slightly to:
case
when `PayTotal` / `PayTargetWeek` <= .05 then 'Under Target'
when `PayTotal` / `PayTargetWeek` > .05 and `PayTotal` / `PayTargetWeek` <= .05 then 'On Target'
when `PayTotal` / `PayTargetWeek` > .05 then 'Above Target'
else 'Not Sure'
endI did this becuase ultimately I didn't need to SUM(`PayTotal`). I removed the AVG() from PayTargetWeek as well.
In the end, the error that was causing the BeastMode to fail validation was the second evalaution in the case, "when `PayTotal` / `PayTargetWeek` > .05 and `PayTotal` / `PayTargetWeek` <= .05 then 'On Target' ". Once I added this, Validation Passed.
Thank you all for the assist and explanations.Chad Bishop
Data Analyst
Bolt Express1
Answers

You'll need to add a check for divide by 0 possibility.
Try this:
CASE WHEN `PayTargetWeek` = 0 THEN 1 ELSE
case when (sum(`PayTotal`) / `PayTargetWeek`) <= .05 then 'Under Target'
when (sum(`PayTotal`) / `PayTargetWeek`) >= .049 and <= .05 then 'On Target'
when (sum(`PayTotal`) / `PayTargetWeek`) >= .051 then 'Above Target'
else 'Not Sure'
endEND
Hopefully that should work for you.
Sincerely,Colt
**Please mark "Accept as Solution" if this post solves your problem
**Say "Thanks" by clicking the "heart" in the post that helped you.0 
Thanks for the quick response...however, this will still *not* resolve.
CASE when `PayTargetWeek` = 0 then 1 ELSE
case when (sum(`PayTotal`) / `PayTargetWeek`) <= .05 then 'Under Target'
when (sum(`PayTotal`) / `PayTargetWeek`) >= .049 and <= .05 then 'On Target'
when (sum(`PayTotal`) / `PayTargetWeek`) >= .051 then 'Above Target'
else 'Not Sure'
end
ENDChad Bishop
Data Analyst
Bolt Express0 
I also tried writing it this way but again...it will *not* resolve/validate.
case when (sum(`PayTotal`) / (CASE when `PayTargetWeek` = 0 then 1 end)) <= .05 then 'Under Target'
when (sum(`PayTotal`) / (CASE when `PayTargetWeek` = 0 then 1 end)) >= .049 and <= .05 then 'On Target'
when (sum(`PayTotal`) / (CASE when `PayTargetWeek` = 0 then 1 end)) >= .051 then 'Above Target'
else 'Not Sure'
endChad Bishop
Data Analyst
Bolt Express0 
Hi Chad
Generally speaking, beast modes with aggregations within case statements are pretty tricky.
Why are you summing PayTotal but not aggregating PayTargetWeek? What your beast mode is doing is adding up a bunch of rows to get the sum of PayTotal, but then comparing the aggregation against a single row's PayTargetWeek value. Comparing aggregates against single rows does not usually work like you want or expect. Is PayTargetWeek the same value for every row that PayTotal is being summed on? Like, a single row of data has an individual PayTotal for a day or person or something but then it also has a wider PayTargetWeek value, that's not the same granularity? You can get around that by averaging your PayTargetWeek value in the denominator (assuming different granularities)
Also, you are missing something in your second comparison. Each comparison needs two values. Your "<= .05" comparison lacks the first value. The aggregation can't carry over. You'll have to compute that aggregation fully in each comparison.
In addition, there might be values between .05 and .049, or .05 and .051, so your would need to adjust the operators to leave no gaps. This won't make your beast mode validate, but it makes the results more usable.
Try this and see what happens:
case
when sum(`PayTotal`) / AVG(`PayTargetWeek`) <= .05 then 'Under Target'
when sum(`PayTotal`) / AVG(`PayTargetWeek`) > .05 and sum(`PayTotal`) / AVG(`PayTargetWeek`) <= .05 then 'On Target'
when sum(`PayTotal`) / AVG(`PayTargetWeek`) > .05 then 'Above Target'
else 'Not Sure'
endAaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 
By the time I opened this thread, SUM(`PayTotal`) was just a troubleshootingitteration of the case() statement I was trying to make work.
I took your suggestion and modified it slightly to:
case
when `PayTotal` / `PayTargetWeek` <= .05 then 'Under Target'
when `PayTotal` / `PayTargetWeek` > .05 and `PayTotal` / `PayTargetWeek` <= .05 then 'On Target'
when `PayTotal` / `PayTargetWeek` > .05 then 'Above Target'
else 'Not Sure'
endI did this becuase ultimately I didn't need to SUM(`PayTotal`). I removed the AVG() from PayTargetWeek as well.
In the end, the error that was causing the BeastMode to fail validation was the second evalaution in the case, "when `PayTotal` / `PayTargetWeek` > .05 and `PayTotal` / `PayTargetWeek` <= .05 then 'On Target' ". Once I added this, Validation Passed.
Thank you all for the assist and explanations.Chad Bishop
Data Analyst
Bolt Express1
Categories
 10.6K All Categories
 8 Connect
 918 Connectors
 250 Workbench
 477 Transform
 1.8K Magic ETL
 69 SQL DataFlows
 478 Datasets
 218 Visualize
 260 Beast Mode
 2.1K Charting
 12 Variables
 19 Automate
 356 APIs & Domo Developer
 89 Apps
 3 Workflows
 20 Predict
 5 Jupyter Workspaces
 15 R & Python Tiles
 249 Distribute
 65 Domo Everywhere
 243 Scheduled Reports
 21 Manage
 42 Governance & Security
 191 Product Ideas
 1.2K Ideas Exchange
 11 Community Forums
 27 Getting Started
 14 Community Member Introductions
 55 Community News
 4.5K Archive