At the moment it seems impossible to display more than 60 rows of data at the same time.
You can’t drag the table to expand to more than about 800 pixels - which is really limiting. (And at the same time there is no option to reduce the count to be 50!)
My client would like to view 500 rows of data in 1 table without having to scroll the wheel in the internal view of the table view. This would also massively help with the “Print as PDF” functionality - as currently it is impossible to actually produce a PDF with 500 lines of data showing in a table.
Anyone had anything else similar to produce, and any workarounds suggested?
Hi @Stoods - Welcome to the Community!
Here is a workaround you can use to get multi page printouts – however it’s through the use of multiple visuals/tables.
Create a calculated field using Rank or DenseRank
Create your table and duplicate for as many pages as you need. (I used 2 for this example)
Filter the visuals for the number of rows that will fit on a page. 1-39, 40-79, etc.
@robdhondt - Thank you so much - awesome workaround
@robdhondt - So just one issue left!!!
So I have the rank displaying - tick!
However - the only way it works is to set all of the other fields in the “group by” field well, and the rank field to be in the “value” field well
Now all works fine doing that - but…
Now I don’t get the option to do a “between” as a filter option
Now - I can add a customer filter, and put to only include 1,2,3,4,5,6,7… etc
This works - but not “elegent”!
Not sure how you got your ranking to be a “between”…
Hi @Stoods - You wouldn’t know it by the name but DenseRank and Rank can use LAA.
You can use something like
Rank([rankby ASC], , PRE_AGG) .
This should solve your needing to have the fields in the field well and the between option.
Fingers crossed this gets you all the way there. Good luck!
So this is fine until you want to add any filters
Its all very close to the functionality I want - just not quite !
I want the post agg ranking - just for it not to be aggregated!!!
I’ll send this to the right team as a feature request. Thanks