Dataset with tables configured with incremental refresh does not respect the RangeStart parameter

[Anonymous]

I have a dataset with a couple of tables that have incremental refresh configured. Due to the size constraint (1 GB limit) I have changed the RangeStart to a more recent date. As expected, my report in Power BI Desktop only shows values from the new RangeStart date. I then published the dataset and refreshed it in Power BI Service.

When I check the values of my report in Power BI Service, I see that the RangeStart parameter is not being respected - I still have values previous to the RangeStart date.

Am I missing something?

[arvindsingh802 · Accepted solution]

RangeStart and RangeEnd are when initially configuring incremental refresh in Power BI Desktop, the parameters are used to filter only a small period of data to be loaded into the model. When published to the service, with the first refresh operation, the service creates incremental refresh and historical partitions based on incremental refresh policy settings, and then overrides the parameter values to filter and query data for each partition based on date/time values for each row.

Incremental refresh for datasets in Power BI - Power BI | Microsoft Docs

[Anonymous]

Does that mean that Power BI Service looks exclusively to the Store rows in the last configuration when it comes to deleting, keeping or loading rows?

Let's say I would change this configuration to 1 year. All the values in this table previous to 2021.12.14 would be deleted in Power BI Service?

[arvindsingh802]

Yes, it will be deleting records in Power BI Web and would only keep records from 14/12/2020 to till date (1 Year)