Forum Discussion
Edit parameter functionality options
Absolutely would take longer but generally you automate the refresh of the data in the Service. Also, Power BI recently released Incremental Refresh so after the initial data load, you could potentially configure incremental refresh to only grab the new data when refreshing the data.
Or, it might make sense in your case to use a Direct Query (live) connection to the database. In that case, you aren't loading any data at all but rather as the user selects dates in the slicer, Power BI is live querying the database to bring back the information. I've seen this scale to millions or even billions of rows of data and it is amazingly fast.
Bottom line, there is no better way to improve the user interface/experience if you are going to do this via query parameters. What you are doing is the best you are going to get right now. It's just how query parameters work. If you want a better user experience, you are going to need to go another route.
Thanks again!
My data comes from connecting multiple huge tables (millions or at least 100s of 1000s of records in each). Without date range in my where clause, wouldn't it take so long for database to get those records to power BI?
Even if Power BI would be able to handle it, I wonder the SQL Server DB engine would take lot longer to get ALL of the data. Isn't it?
When I say "connecting multiple tables", I mean joining tables. Just to be clear. So in power BI, i see a Query1 built that has all the data and Start/End dates as params which are initial filters to reduce the universe to the required volume.