odd beast mode behavior

the_tree
the_tree βšͺ️
edited February 16 in Card Building

Hi- as I was creating a beast mode, I saw that it works great in a single value card, but uses the wrong values in the summary number- same exact beast mode. Any idea on why this would be?

See syntax below. The single value renders the (`Opp Value`)*.05 correctly, whereas the summary number disregards the beast mode calcs and just sums `Opp Value`.

CASE

WHEN `Stage Name` = 'MQL (5%)' THEN sum(`Opp Value`)*.05

END

Thank you!

Best Answer

  • jaeW_at_Onyx
    jaeW_at_Onyx Budapest / Portland, OR 🟀
    Accepted Answer

    @the_tree does it yield the desired results?


    i stated that your code is syntactically correct, look closer at the docs though, in most of them, the CASE statement will be nested INSIDE the aggregation. The only way you get the accurate results with the CASE statement on the outside is IF stage name is on an axis.

Answers

  • GrantSmith
    GrantSmith Indiana 🟀

    Hi @the_tree

    What value do you get as the summary number? What value are you expecting?

  • the_tree
    the_tree βšͺ️
    edited February 16

    I updated the question above

  • jaeW_at_Onyx
    jaeW_at_Onyx Budapest / Portland, OR 🟀
    edited February 16

    @the_tree you can't write that.


    CASE
    
    WHEN `Stage Name` = 'MQL (5%)' THEN sum(`Opp Value`)*.05
    
    END
    


    try

    SUM( 
    CASE
    WHEN `Stage Name` = 'MQL (5%)' THEN `Opp Value` *.05
    END
    )ο»Ώ
    


    your code is syntactically correct, but your SUM(Opp value) is evaluating BEFORE the CASE statement is being tested.

  • the_tree
    the_tree βšͺ️

    It works perfectly everywhere else, and is found in the domo docs as valid syntax

  • the_tree
    the_tree βšͺ️

    Thank you, sorry, I missed that last part, makes sense and it works

Sign In or Register to comment.