odd beast mode behavior

the_tree
the_tree Member
edited February 2021 in Charting

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 Coach
    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.

    Jae Wilson
    Check out my 🎥 Domo Training YouTube Channel 👨‍💻

    **Say "Thanks" by clicking the ❤️ in the post that helped you.
    **Please mark the post that solves your problem by clicking on "Accept as Solution"

Answers

  • GrantSmith
    GrantSmith Coach

    Hi @the_tree

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

    **Was this post helpful? Click Agree or Like below**
    **Did this solve your problem? Accept it as a solution!**
  • the_tree
    the_tree Member
    edited February 2021

    I updated the question above

  • jaeW_at_Onyx
    jaeW_at_Onyx Coach
    edited February 2021

    @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.

    Jae Wilson
    Check out my 🎥 Domo Training YouTube Channel 👨‍💻

    **Say "Thanks" by clicking the ❤️ in the post that helped you.
    **Please mark the post that solves your problem by clicking on "Accept as Solution"
  • the_tree
    the_tree Member

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

  • jaeW_at_Onyx
    jaeW_at_Onyx Coach
    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.

    Jae Wilson
    Check out my 🎥 Domo Training YouTube Channel 👨‍💻

    **Say "Thanks" by clicking the ❤️ in the post that helped you.
    **Please mark the post that solves your problem by clicking on "Accept as Solution"
  • the_tree
    the_tree Member

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

Categories