Forum Discussion
Incremental Refresh | RangeStart vs RangeEnd Parameters?
Hi Anonymous ,
Incremental refresh uses two parameters, named RangeStart and RangeEnd (names are case sensitive). When published, the service will automatically change the parameter values, to load only the data added after the last load, e.g. only for the last day.
Incremental refresh isn't designed to support cases where the filtered date column is updated in the source system, only to load newly added rows. If an update is interpreted as an insertion and a deletion, not an actual update, it might work. If the deletion occurs in the historical range and not the incremental range, it won’t get picked up.
To define the parameters with default values, in the Power Query Editor, select Manage Parameters and add their initial values which will filter the initial load. Once published, the parameter values are overridden automatically by the Power BI service.
With the parameters defined, you can then apply the filter by selecting the Custom Filter menu option for a column.
Ensure rows are filtered where the column value is after or equal to RangeStart and before RangeEnd. Other filter combinations may result in double counting of rows.
Verify queries have an equal to (=) on either RangeStart or RangeEnd, but not both. If the equal to (=) exists on both parameters, a row could satisfy the conditions for two partitions, which could lead to duplicate data in the model, i.e. the same order to be loaded in the model twice in two consecutive loads.
Refer:
https://community.powerbi.com/t5/Community-Blog/Incremental-Refresh-with-Subqueries/ba-p/1003337
https://docs.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overview#refresh-ranges
Did I answer your question? Mark my post as a solution!
Best RegardsLucien
Hi Anonymous ,
Incremental refresh uses two parameters, named RangeStart and RangeEnd (names are case sensitive). When published, the service will automatically change the parameter values, to load only the data added after the last load, e.g. only for the last day.
Incremental refresh isn't designed to support cases where the filtered date column is updated in the source system, only to load newly added rows. If an update is interpreted as an insertion and a deletion, not an actual update, it might work. If the deletion occurs in the historical range and not the incremental range, it won’t get picked up.
To define the parameters with default values, in the Power Query Editor, select Manage Parameters and add their initial values which will filter the initial load. Once published, the parameter values are overridden automatically by the Power BI service.
With the parameters defined, you can then apply the filter by selecting the Custom Filter menu option for a column.
Ensure rows are filtered where the column value is after or equal to RangeStart and before RangeEnd. Other filter combinations may result in double counting of rows.
Verify queries have an equal to (=) on either RangeStart or RangeEnd, but not both. If the equal to (=) exists on both parameters, a row could satisfy the conditions for two partitions, which could lead to duplicate data in the model, i.e. the same order to be loaded in the model twice in two consecutive loads.
Refer:
https://community.powerbi.com/t5/Community-Blog/Incremental-Refresh-with-Subqueries/ba-p/1003337
https://docs.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-overview#refresh-ranges
Did I answer your question? Mark my post as a solution!
Best Regards
Lucien