Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi,
I have an AnalysisServices connection where I am importing tables from Analysis Services by writing a DAX Query inside M:
[Query="EVALUATE
How should I apply Incremental Refresh for this type of connection?
I tried the classic way of filtering the table using the Power Query UI but after the data load I was not able to apply Incremental Refresh on the table in PBI Desktop.
Thanks.
Solved! Go to Solution.
Hi @PImre ,
Hi PImre, when using a DAX query inside Power Query M to import data from an Analysis Services source, applying Incremental Refresh becomes more complex because Power BI's Incremental Refresh relies on native query folding to push date filters to the source system. Since you're manually writing a DAX query, Power BI may not recognize it as foldable or suitable for parameter-driven filtering required for Incremental Refresh setup.
One workaround is to restructure your approach to use a native table import (without a custom DAX query) and apply the date filters using Power Query parameters (RangeStart and RangeEnd) so Power BI can detect and configure Incremental Refresh correctly. Alternatively, if you must use a DAX query, you could dynamically build the query using M code to inject the parameter values, though this requires careful handling and testing to ensure it supports refresh on the Power BI Service.
Hi @PImre,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
Chaithanya.
Hi @PImre ,
Hi PImre, when using a DAX query inside Power Query M to import data from an Analysis Services source, applying Incremental Refresh becomes more complex because Power BI's Incremental Refresh relies on native query folding to push date filters to the source system. Since you're manually writing a DAX query, Power BI may not recognize it as foldable or suitable for parameter-driven filtering required for Incremental Refresh setup.
One workaround is to restructure your approach to use a native table import (without a custom DAX query) and apply the date filters using Power Query parameters (RangeStart and RangeEnd) so Power BI can detect and configure Incremental Refresh correctly. Alternatively, if you must use a DAX query, you could dynamically build the query using M code to inject the parameter values, though this requires careful handling and testing to ensure it supports refresh on the Power BI Service.
Hi @PImre,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
Chaithanya.
Hi @PImre,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
Chaithanya.
please follow the documentation. Configure incremental refresh for Power BI semantic models - Power BI | Microsoft Learn
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 19 | |
| 9 | |
| 8 | |
| 7 | |
| 7 |