Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I have a table payment_trasaction in Power BI based on a simple SELECT from SQL Server
I configured the incremental refresh based on the Account Status date
between start_date and end_date which are the same 2/1/2024 00:00:00 AM (they are updated in the PBI service based on the refresh)
now when I check the config on it :
archive data starting from 10 years before refresh date
incrementally refresh data starting 31 days before refresh dare
no optional setting
the last time I refreshed the data set is 5/23/2024 and the Account Status date doesn't contain consecutive dates.
What do you think of the way the incremental refresh is configired?
when i check the table in power bi it has only data for may
but not for the months before
knowing that I skip the refresh for the weekends and the
Solved! Go to Solution.
Hi @AmiraBedh ,
Based on the description, an incremental refresh policy to partition the table, refreshing only the most recent import partitions, and optionally using another DirectQuery partition for real-time data can significantly reduce the amount of data that has to be refreshed. With incremental refresh, refreshes are faster and refreshes are more reliable.
For configuring policy, RangeStart and RangeEnd parameters are used to filter only a small period of data that’s loaded into the model.
In Archive data starting, specify the historical store period included in the model.
In Incrementally refresh data starting, specify the refresh period.
You can also view the following documents to learn more information.
Incremental refresh for semantic models and real-time data in Power BI - Power BI | Microsoft Learn
Troubleshoot incremental refresh and real-time data - Power BI | Microsoft Learn
Best Regards,
Wisdom Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @AmiraBedh ,
Based on the description, an incremental refresh policy to partition the table, refreshing only the most recent import partitions, and optionally using another DirectQuery partition for real-time data can significantly reduce the amount of data that has to be refreshed. With incremental refresh, refreshes are faster and refreshes are more reliable.
For configuring policy, RangeStart and RangeEnd parameters are used to filter only a small period of data that’s loaded into the model.
In Archive data starting, specify the historical store period included in the model.
In Incrementally refresh data starting, specify the refresh period.
You can also view the following documents to learn more information.
Incremental refresh for semantic models and real-time data in Power BI - Power BI | Microsoft Learn
Troubleshoot incremental refresh and real-time data - Power BI | Microsoft Learn
Best Regards,
Wisdom Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I can't understand this part : optionally using another DirectQuery partition for real-time data
Since I am using Azure databases and not SSAS any workaround to check the partitions if possible ?
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
80 | |
76 | |
61 | |
36 | |
32 |
User | Count |
---|---|
91 | |
60 | |
59 | |
49 | |
45 |