<@U4T9UPF3L> I'd love to take a stab at your formu...
# suiteanalytics
k
@NS.TX I'd love to take a stab at your formula - but unfortunately, that's one where you really need data to troubleshoot/try it, and a couple hours. The biggest troubleshooting advice I can give you - is NS doesn't like mismatch in summary level within your formula. So if you can figure out how to redo your formula to have the sums at all stages of it, it should be able to be done.
n
@KevinJ of Kansas How about reviewing this formula that keeps resulting in an 'unexpected error': case when sum({durationdecimal}) <= 44 then (sum({durationdecimal})*({laborcost})) else (sum({durationdecimal})-((sum({durationdecimal})-44)*{laborcost})) end
the formula after then is breaking it
k
Copy code
case when sum({durationdecimal}) <= 44 then sum({durationdecimal}*{laborcost}) else max(sum({durationdecimal}-44)*{laborcost})  end
is my guess
Nope I was wrong. gotta fix it - Fixed
summary type on that should be max or min by the way
n
curious - why does the summary type need to be min or max
k
If you do a sum - it will do that formula for each row of results. So you'll "sum" your "sums" and get bad data
Did the formula work or still unexpected error?
n
it took the formula, but invalid expression
k
Try this
Copy code
case when sum({durationdecimal}) <= 44 then sum({durationdecimal}*{laborcost}) else max(sum({durationdecimal}-44)*max({laborcost}))  end
That's probably my last "free" attempt! Got too much billable work to be doing to spend more working on this one!
one last one
Copy code
case when sum({durationdecimal}) <= 44 then sum({durationdecimal}*{laborcost}) else max((sum({durationdecimal})-44)*max({laborcost}))  end
Darn parenthesis gotta be balanced.
n
Fair enough
I'll keep working on it
k
Like I said at the start - probably a couple hour problem
n
if i figure out why im getting the invalid expression error, i'll lyk
Ty for the guidance
k
best bet is to break it out into it's components
figure out which components evaluate correctly
adjust the ones that don't
n
@KevinJ of Kansas ty for the assist yesterday, I'm still working on it, but i've made progress, and your insight was integral to that progress