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!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
I want to get a clear understanding of the Refresh rows from the past field.
Is this the correct interpretation of my setting:
If this is correct, then any row created older than 1 year ago won't be refreshed even if updated recently?
Then I'd have to set the Refresh rows from the past value to be equal to Store rows from the past?
Thanks
Solved! Go to Solution.
Is this the correct interpretation of my setting:
keep the past 10 years data
look for the rows created in the past 1 year
of the past 1 year data, refresh rows where updated column changed
Not exactly. What is actually means is
- keep 8 or 9 static (cold) yearly partitions
- no warm partitions (as there is no granularity difference)
- 1 or 2 hot yearly partitions. 2023 will be refreshed as long as parts of it are still "within one calendar year from today". NOTE: Incremental refresh only works with regular calendar boundaries
"Detect Data Changes" will incur additional storage cost as your partitions will be canaried (duplicated) so the Power BI service can decide when to update them. Not recommended.
"Only refresh complete years" will exclude the current year from refresh. Not sure why you would want that.
Is this the correct interpretation of my setting:
keep the past 10 years data
look for the rows created in the past 1 year
of the past 1 year data, refresh rows where updated column changed
Not exactly. What is actually means is
- keep 8 or 9 static (cold) yearly partitions
- no warm partitions (as there is no granularity difference)
- 1 or 2 hot yearly partitions. 2023 will be refreshed as long as parts of it are still "within one calendar year from today". NOTE: Incremental refresh only works with regular calendar boundaries
"Detect Data Changes" will incur additional storage cost as your partitions will be canaried (duplicated) so the Power BI service can decide when to update them. Not recommended.
"Only refresh complete years" will exclude the current year from refresh. Not sure why you would want that.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.