Limiting Pivot Values

---

@Cartergan wrote:

You can try limiting the data rows and see if this achieves the result you are looking for. In the analyzer view near the bottom right of the screen you can set how many rows you'd like to show, and then you'd need to sort your results how you'd like them to appear. 

 

---

I would be unsurprised if this method yielded unexpected results, so test carefully.  I do not believe that LIMIT N rows would distribute across all the dimension members (combinations of Cat1 > Cat2).  More likely, if it's anything like SQL, i suspect it would just take the first N rows without respect to distribution.  an explicit ORDER BY clause may appear to help, but i would proceed with caution.

Given my assumption is true, you could try to use logic to force the visualization you want.

"for each cat1 i want to keep the 3 highest ranked rows."

you could try to calculate RANK() and THEN assign a value based on RANK (using a CASE) and set a LIMIT based on a predefined number of CAT1 rows * 3 rank ( ex. LIMIT = 4 *3) 

FIRST calculate RANK

rank() over (partition by cat1 order by sum(amount) desc)

THEN assign amount_value based on CASE

CASE WHEN rank() over (partition by cat1 order by sum(amount) desc) > 4 then -1000 else sum(amount) end

I didn't test this pseudo code at all... but the idea is, if the row_rank is greater than 4 then you want to exclude it, so you assign it an extreme value.  If you're limiting rows, then all extreme values should hopefully be excluded.  I chose row_rank = 4 in the unlikely event of ties, but that messes with your LIMIT.

To use windowed functions in beast modes email your CSM (customer success manager) and ask them to enable 'windowed functions in beast modes'.

Additionally, cc @MarkSnodgrass , @DataMaven , @GrantSmith @swagner , you can ask your CSM to enable 'filter on aggregates' which would allow you to filter on the HAVING clause of a SQL statement in your cards.  I personally recommend this with EXTREME caveats insofar as, AFAIK this functionality was rapidly implemented and not thoroughly integrated into card builder.  so... use at your own risk and test it a lot.