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.
Hi team,
I have a Power BI Report published in Premium Capacity Workspace. The last 5 days the report even though it is refresh as normal (schedule refresh with no incident or warning) doen't bring the latest data to the fact tables. The Fact Tables doesn't have the 5 last days data, even though other tables are refreshed. For example, I have a table where I gather all the process run ids of all the tables I use as sources for my report in order to control the input, and this table is refreshed normally. But the fact tables not. For the fact tables I have Incremental refresh set up, Archiving 2 years and refresh window 7 days.
I would also like to note that the report has been live in the Service for over three months, running daily refreshes, and we have never encountered a similar issue before. This behavior started appearing over the last 5 days.
Thank you in advance,
Eleftheria
Solved! Go to Solution.
Hi @elia22gr ,
Since the report works correctly after a full refresh but then starts missing recent data again, it’s helpful to look beyond just the parameter configuration. Begin by confirming that your fact table query still preserves proper query folding, as any transformation that breaks folding before the incremental filter can prevent the Service from identifying and loading new records correctly. In parallel, review how the incremental refresh partitions behave in the Service (via XMLA/SSMS), as there are situations where a refresh completes successfully but the partitions themselves are not updated with new data.
It’s also important to verify that the missing records actually fall within your configured 7-day refresh window, since factors such as timezone differences or delayed source ingestion can push data outside the incremental range. As a validation step, you can temporarily disable incremental refresh and perform a full refresh to confirm whether the issue is specifically linked to partition logic rather than the underlying data source.
Additionally, take a closer look at the fact table query to ensure that no transformations or calculated columns are interfering with filter pushdown, as this can quietly impact incremental refresh behavior. Finally, because the issue appeared after a long period of stable operation, it may indicate a potential service-side inconsistency. In such cases, capturing details about partition behavior and refresh activity can help if escalation is needed. Republishing the dataset and app can also be useful to rule out any caching inconsistencies, even though it is less likely to be the primary cause.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support
Hi @elia22gr ,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support
Hi @elia22gr ,
We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support
Hi @elia22gr ,
Since the report works correctly after a full refresh but then starts missing recent data again, it’s helpful to look beyond just the parameter configuration. Begin by confirming that your fact table query still preserves proper query folding, as any transformation that breaks folding before the incremental filter can prevent the Service from identifying and loading new records correctly. In parallel, review how the incremental refresh partitions behave in the Service (via XMLA/SSMS), as there are situations where a refresh completes successfully but the partitions themselves are not updated with new data.
It’s also important to verify that the missing records actually fall within your configured 7-day refresh window, since factors such as timezone differences or delayed source ingestion can push data outside the incremental range. As a validation step, you can temporarily disable incremental refresh and perform a full refresh to confirm whether the issue is specifically linked to partition logic rather than the underlying data source.
Additionally, take a closer look at the fact table query to ensure that no transformations or calculated columns are interfering with filter pushdown, as this can quietly impact incremental refresh behavior. Finally, because the issue appeared after a long period of stable operation, it may indicate a potential service-side inconsistency. In such cases, capturing details about partition behavior and refresh activity can help if escalation is needed. Republishing the dataset and app can also be useful to rule out any caching inconsistencies, even though it is less likely to be the primary cause.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support
From the App. But regardless from where you access the report, we have missing data & pages in not correct order displayed.
Are users accessing the report from the workspace or from the app?
Another weird thing that I am phasing with this report is I am changing the order of the pages in Service and even though that is saved when I reopen the report it doesn't. It keeps all the other change except this. The same goes for the Desktop file as well.
In Desktop I have the end of the month, in service it doesn't need to
Hi @elia22gr ,This is an interesting issue. Could you share the PQ for the fact table, along with the parameter values you have defined for range start and range end ? Sharing the PBIX file would be even better.
If the refresh was working for the last three months without any problems, and it's now failing to pick up data, this strongly suggests an issue with the parameters or the PQ filters.
Thanks
Thank you for your reply.
The Power Query parameters haven't changes since the begining neither did the columns in my fact tables used in incremental refresh. Also, when I run it in desktop everything works fine. Yesterday, I re published the report so I force it to run a full refresh and it worked fine, but today I encountered the issue again. I tried to run full refresh via Management studio and althought it said that it was successful the data didn't appear.
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 |
|---|---|
| 15 | |
| 11 | |
| 9 | |
| 7 | |
| 6 |
| User | Count |
|---|---|
| 43 | |
| 33 | |
| 29 | |
| 23 | |
| 20 |