# Beast Mode error message (dividing by zero)

We're trying to find the variance of Actual from Forecasted but running into the Zero Division issue; read a few other threads, all of which were far more involved Beast Mode formulas, and tried as best I could to adapt those formulas to our situation but having trouble getting it to work - any help would be greatly appreciated!

Original Beast Mode Calculation (validated fine but obviously returned an error message when the Beast Mode was saved: You have a divide by zero error in your Card’s Beast Mode)

SUM(`Actual Call Volume`) / SUM(`Forecasted Call Volume`)

After reading other threads tried several possible solutions and thought this made the most sense, and seemed straightforward but can't get it to validate & not sure what needs to be corrected:

CASE
WHEN SUM(`Forecasted Call Volume`) = 0
THEN 'No Variance'
ELSE
SUM(`Actual Call Volume`) / SUM(`Forecasted Call Volume`)

The above formula was tried with several variances as well and still no luck. Any thoughts on what we're missing here? If additional information is required, please don't hesitate to ask and thank you in advance for your time & assistance!

I think the problem is if the case statement is true, you're returning a string but when it's false, you have it returning a number. they need to be the same.

Hi,

I think @Godzilla is right.

Another way to tackle this would be :

SUM(`Actual Call Volume`) / NULLIF(SUM(`Forecasted Call Volume`),0)

Hope this helps.

• @Godzilla, tried to change 'No Variance' to '' (empty single quotes) as well as '0' (numeric) to make it so both returned a numeric value rather than a string & numeric value, but neither worked.

Once last question: by removing No Variance and keeping an empty single quotes, or placing a zero in between, in theory wouldn't at least one of those options have worked to make the formula valid?

You guys are always so helpful, and very quick to reply and it's greatly appreciated!

• I believe since you kept the single quotes around the 0, i think it still treated the vaue as a string. For numeric values, you do not need any quotation  around them.

• Thanks for the clarification, @Godzilla, much appreciated!