Forum Discussion
Prompt Page
My advice is this. Don't try to do it the way you have done it in the past with your old systems. Instead think abou the problem and then try to solve the problem with the new tools you have. eg. Problem: User needs to select what the report shows. Solution: you have report filters, slicers, cross filtering etc.
Give it a go with this mind set - you will be amazed.
Sometimes I prefer the prompt page,
Suppose you have 5000 users running 10 reports per day, and 3 of them, are reports that performs realtime heavy calculations. Suppose the reports take just 1 minute. So, 5000 * 3 = 15000 minutes processing time lost.
I plan to move Excel reports with macro and stored procedures to PowerBI, and the prompt page could be a good feauture.
Anything that you're doing that currently takes 3 minutes to calculate every time a user tries to load a report is probably something that can be done more efficiently in a different way. Likely involving a data warehouse.
In any case you can write measures to use disconnected slicers that allow users to pick a number. The measure can use the selected number in the slicer as a variable and feed it into a TOPN function perhaps as a method of limiting a number of records.
Hi
Understand that there are different level of reporting. For operational reports, you should have prompts (why kill db) and for analytical reports you might bring most part of the data ( get the haystack) and then look for the needle. Power BI is not a operational BI tool.
Thanks
RP
