Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!

Reply
Anonymous
Not applicable

Incremental refresh settings clarification

pbi_inc_ref_set.png

I want to get a clear understanding of the Refresh rows from the past field.

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

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

1 ACCEPTED SOLUTION
lbendlin
Super User
Super User

 

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.

 

Advanced incremental refresh and real-time data with the XMLA endpoint in Power BI - Power BI | Micr...

View solution in original post

1 REPLY 1
lbendlin
Super User
Super User

 

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.

 

Advanced incremental refresh and real-time data with the XMLA endpoint in Power BI - Power BI | Micr...

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

Vote for your favorite vizzies from the Power BI World Championship submissions!

Sticker Challenge 2026 Carousel

Join our Community Sticker Challenge 2026

If you love stickers, then you will definitely want to check out our Community Sticker Challenge!

January Power BI Update Carousel

Power BI Monthly Update - January 2026

Check out the January 2026 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.