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

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.

Reply
T_W12
Regular Visitor

Incremental Refresh duplicates existing data instead of replacing it with updated variant

Hi,

 

New to power bi and I've set up some charts for a client and due to their growing influx of data, am trying to implement an incremental refresh so that we only add new data or replace existing data that may have been updated the day before. However, I keep encountering a problem where the incremental refresh adds the updated data on top of the existing data instead of replacing it, essentially duplicating it. 

 

I've looked on other forums for similar problems and workarounds but there doesn't seem to be much about it. I understand query folding is neccessary when implementing an incremental refresh however it always is disabled (i.e. greyed out) when I come to enabling it. There was a number of fields types I needed to manually change when originally importing the data as we encountered issues where dates and times were being stored in US format instead of UK when we published it, so I'm not sure if that could be the reason for query folding being disabled.

 

Anyway, I'm at a bit of a loss as to why the incremental refresh seems to be duplicating the data rather than just replacing the existing data with the updated variant. Would greatly appreciate any advice from someone who may have experienced a similar issue or knows of a workaround.

 

Thanks for any help.

1 REPLY 1
lbendlin
Super User
Super User

"I understand query folding is neccessary when implementing an incremental refresh "

No, that is not accurate. While highly recommended, query folding is not a strict requirement for incremental refresh.

 

Your problem is different. What you actually want is differential refresh, not incremental refresh. Incremental refresh expects data to be immutable. Your data changes after the fact. To mitigate that you need to come up with a slightly different strategy, extending the lookback period in a way that you catch the majority of data changes. Another approach is to have transaction IDs in your data that identify the change cadence for your data rows, and allows you to pick only the latest version of each transaction.

 

Hopefully one day Power BI will support differential refresh.

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 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.