I would do it as you have described. Take revenue from the details-table. We have tables with >30 mio records and (unless you show every individual record) Sisense handles this fine. No long loading times. And its easy in use for users.
Using Jump to Dashboard is nice, but it does add an extra load as a new dashboard needs to be loaded.
You could also think about single-select filtering on year(or month etc) to avoid loading to many records.
As a final solution , you could check out the Expandable Pivots of the premium partners. Those support expanding and collapsing fields and also determine how many records are loaded on the first go and how many records may be loaded when the user presses the button.
Good luck
Thanks again for the different insights!
Can I know what type of datasource you connected to in Sisense?
As the loading speeds vary right with different types of Datasources. Just curious as Our's would be more than 100's of million's of records that too using Traditional SQL Server and not cloud based.
For our tables that are this big, we do not use live-query as that would put a big strain on our DB-server. We import the records into the elasticube (datasource is MySQL) and build/query it from there without any issues. In our case importing we can do via accumulative builds. Speeds things up
