Forum Discussion
Impactful IndividualDetect Data Changes - Incremental refresh
Hi powerbiexpert22,
This comes down to how Detect data changes works. It doesn't look at single rows. For each partition inside the refresh window, Power BI stores the highest modifieddate it saw. On the next refresh it reprocesses that partition only if the new highest value is later than the stored one.
So two things can hide your edit. If ID 25 sits in a partition where another row already has a later modifieddate, the highest value didn't change and the partition is skipped. And partitions are split by the RangeStart/RangeEnd column (for example the created or order date), not by modifieddate. If ID 25's date falls in the archived part of the policy, it is never refreshed incrementally at all.
Also note that Desktop doesn't apply incremental refresh. This behaviour only shows after publishing to the Service.
To confirm, connect to the XMLA endpoint with SSMS or Tabular Editor and look at the partition that holds ID 25. To force the change in, refresh that one partition, or widen the refresh window for a run. If old rows get edited regularly, a refresh window long enough to cover your usual edits is the cleaner fix.
Resolver IHi powerbiexpert22,
This comes down to how Detect data changes works. It doesn't look at single rows. For each partition inside the refresh window, Power BI stores the highest modifieddate it saw. On the next refresh it reprocesses that partition only if the new highest value is later than the stored one.
So two things can hide your edit. If ID 25 sits in a partition where another row already has a later modifieddate, the highest value didn't change and the partition is skipped. And partitions are split by the RangeStart/RangeEnd column (for example the created or order date), not by modifieddate. If ID 25's date falls in the archived part of the policy, it is never refreshed incrementally at all.
Also note that Desktop doesn't apply incremental refresh. This behaviour only shows after publishing to the Service.
To confirm, connect to the XMLA endpoint with SSMS or Tabular Editor and look at the partition that holds ID 25. To force the change in, refresh that one partition, or widen the refresh window for a run. If old rows get edited regularly, a refresh window long enough to cover your usual edits is the cleaner fix.