Incremental refresh - Alternate RangeStart and RangeEnd

[Marc-Alexis]

Dear PBI gurus,

I am currently implementing a model with the incremental refresh functionality.

The issue I am facing is that one of the tables would require alternate RangeStart and RangeEnd than the other tables.

Since RangeStart and RangeEnd are reserved, I was wondering there was a way to sort of create RangeStart2 and RangeEnd2 which would still enable the incremental refresh.

Thanks in advance for your help!

[v-lionel-msft]

Hi @Marc-Alexis ,

No, It's impossible to achieve the idea in current version( 2.81.5831.821 64-bit (May 2020)).

But you don't need to set two sets of parameters.

All You Need to Know About the Incremental Refresh in Power BI: Load Changes Only 

Best regards,
Lionel Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Best regards,
Lionel Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Marc-Alexis · Accepted solution]

Hello Lionel,

Thank you for your answer. Actually, whilst it is indeed impossible to set alternate RangeStart nor RangeEnd, it is possible at a later stage to change different archive and refresh periods by table.

I will confirm when fully implemented

[JWedge]

It is possible to modify RangeStart and RangeEnd using functions in Power Query (checkout guyinacubes latest youtube video for how to implement this)

[amitchandak]

@Marc-Alexis , Can you explain with an example.

I think every table can have its won date if needed

https://radacad.com/all-you-need-to-know-about-the-incremental-refresh-in-power-bi-load-changes-only

[Marc-Alexis]

For instance, 3 tables are relying on a RangeStart=01/01/2017 and RangeEnd=01/01/2050 with the rows in the past 3 years stored and a resfresh for the rows in the last 60 days.

The other table of the same PBI would require an incremental refresh with the following attributes:

RangeStart=01/01/2000 and RangeEnd=01/01/2050 with also the rows in the past 3 years stored and a resfresh for the rows in the last 60 days.