Forum Discussion
Incremental Refresh, Detect changes not working
That is by design. "warm" partitions are not part of the change tracking.
Extend your "hot" window. For example 60 days instead of 14.
Think of the participating partitions. You specified 14 days/ 24 months. That means the "hot" refreshes will flush and fill the most recent 14 day partitions, but ONLY if the AdjustedDate in these partitions is different. If the AdjustedDate for partition "today minus 12" didn't change then the partition will not be refreshed even though it is a member of the "last 14 days" group.
Hi Ibendlin, and thanks for the response.
But the AdjustedDate has changed. Everytime I make a change to the values I run GETDATE() to get the current datetime on the value in AdjustedDate.
Have you given the Power BI Service a chance to actually set up the partitions and fill them? Every time you make structural changes to your report and/or semantic model the incremental partitions will be reset.
I believe so. I even rebuilt the dataflow from the ground up with the final settings for Incremental Refresh.
I have gotten one step further though - if I update values where CallDate is within the 14 days, these updates get picked up in the refresh. But I still can't get updated values for records where CallDate is before 14 days and AdjustedDate is within 14 days.
That is by design. "warm" partitions are not part of the change tracking.
Extend your "hot" window. For example 60 days instead of 14.