Forum Discussion
Incremental refresh for custom connector with call to REST API: RangeStart and RangeEnd
Finally we found the solution:
It is all up to query folding. The article helped a lot:
https://bengribaudo.com/blog/2022/01/20/6500/power-query-m-primer-part-23-query-folding-i
One does not need to define RangeStart nor RangeEnd parameters anywhere in the connector.
Instead one should implement Table.View as shown here:
https://learn.microsoft.com/en-us/power-query/samples/trippin/10-tableview1/readmeThe only missing information is that one need to implement OnSelectRows.
Further information:
https://community.fabric.microsoft.com/t5/Power-Query/Query-folding-Table-View-handler-function-to-filter-rows-add/td-p/3154149br, Michael
RangeStart and RangeEnd is upercase at the shared function. Do you mean it should be upercase on the other functions as well?
Or can you give an example to see where exactly those params get injected?
By the way, the url can not be precompiled because we need our customer to connect to his individual endpoint.
Many thanks for your help so far.
Incremental refresh only works on partition level. I cannot see how you would be able to add additional filters like your customer name. Are you expecting this to address different partitions?
Let's take a step back. What is your primary reason for trying to use Incremental Refresh?
We want to reduce the amount of data to be transfered. We configured to load factData for the last 5 years into the archive partition, so only once. The last 3 month should load on every refresh to get the latest data. So we applied incremental refresh on a timestamp-columd.
Will you have separate semantic models for each of the customers?
yes! But we are talking about a custom connector. From other posts I learned, that custom connectors have the ability for incremental refresh. Unfortunately I can not find any samples online.