Use pfilter to limit data to 50 rows

Gijs
Gijs Amsterdam, Netherlands ⚪️

For an embedded card, we want to limit the used rows for the visualisation to eg 50.

 

We use PFILTERS to filter the data for a specific client, so that data is already filtered. Is there a way to limit the data to the most recent 50 rows? (the card is already sorted by date column)

Comments

  • GrantSmith
    GrantSmith Indiana 🔴

    Hi @user006513 

     

    Have you tried applying a row limit to your table to be 50? (Data Table > Row Limit - Just below the Add Calculated Field button on the column list)

     

    Screen Shot 2020-06-23 at 1.02.24 PM.png

  • Yes that "row limit" seems to do the trick, but is there a way to apply that dynamically? via the pfilters preferably ?

  • GrantSmith
    GrantSmith Indiana 🔴

    Using row limit, no, pfilters won't affect that setting.

     

    You might be able to use a windowing function to calculate the row number and then use a pfilter to filter the beast mode (this requires two feature switches on your instance, one for the windowing functions and another for filtering aggregates - talk with your CSM). I haven't tested this before so I can't guarantee it'll work but would be worth a try.

     

    Row Number example beast mode

    SUM(SUM(1)) OVER (ORDER BY `Date`)

     

  • jaeW_at_Onyx
    jaeW_at_Onyx Budapest / Portland, OR 🟤

    @GrantSmith remember, you can't filter on a windowed function b/c that's functionally the same as filtering on the HAVING clause (unless you have the beta feature enabled, but even then ... could be janky.

     

    I don't think @chrishaleua  have you seen anything like this baked into product without using embedded cards or anything custom?

  • GrantSmith
    GrantSmith Indiana 🔴

    @jaeW_at_Onyx - Right, that's why I suggested to talk to the CSM to possibly having both the windowing function and the aggregate / windowing filters enabled. You are correct in that it might not have the expected results at times and is still sort of use at your own risk.

  • That beast mode calculated field seems to do the trick! Thanks for the suggestion!

This discussion has been closed.