Forum Discussion
Incremental Refresh - Duplicate Rows for Refresh Window
Hi,
I've set up Incremental Refresh on my PBIX file. When checking the PBIX file against the Power BI Service, I noticed that the results for the Refresh Window in the Service are double that of the PBIX file.
When I had a closer look at this it appears there are double the amount of rows in the Service than the PBIX file. As below:
PBIX:
Service:
I've had a look around and can see that some users have been advised to check View Native Query in Power Query. However this is greyed out for me. I'm passing a number of parameters through my SQL statement and thought this could be the cause. But I've just tried building a simple connection without parameters and View Native Query is still unavailable.
Do I need to create a unique ID for each row? At the moment there are multiple ID fields but not one specifically for each row.
Any ideas on how I can resolve this? I have a huge volume of data to refresh and could do with implementing an incremental refresh to deal with this.
Thanks,
Mark
Hi lbendlin ,
I think I understand now. I've set the RangeStart parameter to filter to dates AFTER and the RangeEnd parameter to filter dates BEFORE or EQUAL TO. Previously they both had EQUAL TO in the filter.
This seems to have corrected it.Thanks,
Mark
3 Replies
there can be many reasons for your symptoms. Maybe you can provide more details on your setup
- parameters must be datetime or datenumber
- parameters cannot both be inclusive
- incremental refresh does not account for scenarios where older data gets changed.
Incremental refresh for datasets and real-time data in Power BI - Power BI | Microsoft Docs
Hi lbendlin ,
Thanks for replying. I can confirm that my RangeStart and RangeEnd parameters are DateTime formatted, as below:
When you say that parameters cannot both be inclusive, what do you mean by this?
On your final point, this is understood. I've set my refresh window to be 60 days, which should be enough of a window to catch anything that changes.
Thanks,
Mark
Hi lbendlin ,
I think I understand now. I've set the RangeStart parameter to filter to dates AFTER and the RangeEnd parameter to filter dates BEFORE or EQUAL TO. Previously they both had EQUAL TO in the filter.
This seems to have corrected it.Thanks,
Mark
