david_cunningham Coach

@jimsteph yes! Great idea. most of the time I'm making changes at the tail end, and just need to test a few new tiles added. I would also think this would be advantageous for Domo because it would minimize unnecessary reprocessing…

@TMonty0319 I'm confused. It sounds like the output you're seeking is the exact output that I showed in my post? Let me know if there is something I'm missing about your request, or if there is a particular part of implementing my proposed solution that you're getting stuck on. I'm happy to troubleshoot with you.

@TMonty0319 Here is a more detailed example. You can see below that the following outcomes are expected. C=Complete NC=NotComplete The above output is a pivot table. For the sake of clarity, below is an example where I replicate your error. You can see that if I don't use the beast mode to aggregate, I can replicate the…

I would suggest doing a beast mode as follows CASE WHEN taskEventStatus = 'Completed' OR taskEventStatus = 'CompleteLate' THEN 0 ELSE 1 END Then nest that within another case statement CASE WHEN SUM(CASE WHEN taskEventStatus = 'Completed' OR taskEventStatus = 'CompleteLate' THEN 0 ELSE 1 END) = 0 then 'Yes' else 'No' end…

You could do CASE WHEN fruit in ('Apple','Orange','Pear') THEN CASE WHEN Fruit= 'Apple' and Achieved Value >= 3 then 'ABOVE' WHEN Fruit= 'Orange' and Achieved Value >= 5 then 'ABOVE' WHEN Fruit= 'Pear' and Achieved Value >= 2 THEN 'ABOVE' ELSE 'BELOW' END ELSE 'N/A' END