This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
I'm working with a dataset in a data warehouse. It is a very large dataset but I suspect in most cases the users will only be querying newer data. I think a Direct Query solution will likely work, but I wondered what the best place is to put in my date filters would be. Is it better to insert these filters at the Power Query level or in Power BI? Or does it matter since the queries are only actually sent when a visualization is refreshed?
Theoretically, then, I could insert a report-level filter for dates and have that set as default but allow report viewers to change it if for some reason they want to query older data? In most cases that should keep performance within reasonable bounds, right? If that works, it seems like a nice compromise.
Solved! Go to Solution.
Doesn't really matter in Direct Query but you can use Power Query as a sort of safety net. Whatever the users filter in the UI will be added to the Power Query filters.
Doesn't really matter in Direct Query but you can use Power Query as a sort of safety net. Whatever the users filter in the UI will be added to the Power Query filters.
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 25 | |
| 24 | |
| 22 | |
| 19 | |
| 18 |
| User | Count |
|---|---|
| 44 | |
| 42 | |
| 42 | |
| 21 | |
| 21 |