I have tio dispaly a detail table which has 4 dinms and around 35 expressions.
Currently my dashboard has around 11 million rows.So in order to limit the number of displayed in the details table (straight table) I have used a calculation condition in the st table.So the user is forced to pick a year and a month ( helps me the limit the number of rows displayed to around 50 to 60 k). Which is still a big number.The users plan to export the results to excel( which makes the problem worse,because the amount of bandwidth used when 10 or more users decide to export 50 k rows concurrently)
I feel pagination is the solution to this problem ,I found a number of articles on this (see below)
The downside of this approach is the user is forced to select the dims that are specified in the calculation condition.
I want the user to be able to select any dimension from the available filters (The table shouldn't display anything till user makes a selelction).
Only first 1000 rows should be displayed ,when the selection is make ( for some reason I'm getting more than 1000 rows in the first page when I try to implelent pagination ),then the user can go to next 1000 rows by clicking on the next button .