How can I fix this Beast Mode Window Function to display the proper value in the total row?

MosesWynn 🟡
edited August 2021 in Card Building

I have the following table that is using window functions in beast mode to calculate pipeline coverage.

I have these window functions for calculating the visible visible columns:

SUM(CASE WHEN LEFT(`Stage`, 1) != '7' THEN `Pipeline` END)

OVER (PARTITION BY `Selling Lane`)
Late Stage/AOP
SUM(CASE WHEN LEFT(`Stage`, 1) IN ('3','4','5','6') THEN `Pipeline` END)

OVER (PARTITION BY `Selling Lane`)

Each Selling Lane has a specific AOP and there are multiple records for each selling lane.

The issue is the total row is showing the sum for each of the Selling Lanes' coverages instead of the total aggregation. I'm assuming this is because I have the partition by clause included in there, which is needed to calculate it for each selling lane. Is there a way that I can get the total row to show the aggregate overall instead of the sum for each of the selling lanes?

Best Answers

  • GrantSmith
    GrantSmith Indiana 🥷
    Answer ✓

    The total row adds everything after beast modes have been applied. You’ll need to stack your data in an ETL using an append with your data set grouped and summed and call the rows TOTAL. Then you can use the beast mode to calculate your data for each lane and the total

    **Was this post helpful? Click Agree or Like below**

    **Did this solve your problem? Accept it as a solution!**
  • jaeW_at_Onyx
    jaeW_at_Onyx Budapest / Portland, OR 🟤
    Answer ✓

    I don't quite understand what you're trying to accomplish, but this is syntactically incorrect (for analyzer) ... it's fine for standard SQL. But this window function MIN(AOP) will not aggregate as expected.

    SUM(CASE WHEN LEFT(`Stage`, 1) IN ('3','4','5','6') THEN `Pipeline` END)
    OVER (PARTITION BY `Selling Lane`)

    Window functions in Analyzer must always include two aggregations b/c the windowing happens AFTER the initial GROUP BY clause is applied.

    In the below example, by taking SUM(AOP) for each row of your displayed axis, and then taking the MIN of each SUM() you're finding the minimum aggregated AOP across all your rows.

    If you did it the other way around SUM(MIN(AOP) you'd find the minimum AOP for each group and then sum the MIN(AOP) across all groups.

    SUM(CASE WHEN LEFT(`Stage`, 1) IN ('3','4','5','6') THEN `Pipeline` END)
    MIN(SUM(`AOP`)) OVER (PARTITION BY `Selling Lane`)

    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"


  • @jaeW_at_Onyx Are you able to answer this?

  • MarkSnodgrass
    MarkSnodgrass Portland, Oregon 🥷

    Did you try this?

    SUM(CASE WHEN LEFT(`Stage`, 1) != '7' THEN `Pipeline` END) OVER ()
    MIN(`AOP`) OVER(PARTITION BY `SF Selling Lane`)

    **Make sure to <3 any users posts that helped you.
    **Please mark as accepted the ones who solved your issue.
  • @MarkSnodgrass

    Thanks for your response! Unfortunately that seems not to have worked. Doing that breaks the aggregation by selling lane and shows the overall aggregation * number of records in the total row.