Forum Discussion
Incremental Refresh on Compute Entities
This has been a while since I posted the original question. We have implemented the incremental refresh between dataflows (for example, staging and processing dataflows) and it's been working excellent.
The confusion is between linked and compute entities, as mentioned above. The linked entities cannot be changed from downstream dataflows and so the question does not apply to them. But if you load your original data into a compute entity, then it is possible to implement IR between them.
In our case, it reduced the downstream processing of a large dataflow table (~500 million rows) from 4 hours to about 20 minutes.
You are reading the Microsoft Article right, Incremental refresh between dataflows is not required if the source dataflow has incremental refresh implemented.
If this post helps, then please consider Accept it as the solution, Appreciate your Kudos!
Thanks for your reply. Does it mean that incremental refresh logic implemented at the source is propagated throughout all linked entities? Can you post a link to where I can read more?
I was wondering the exact same thing myself - definitely interested to hear the answer.
Hi
I am wondering how you finally solved this challenge as I am in the same situation. Could you kindly share your feedback?
Thanks!
I would also like to read the specifics on this.
Yes, linked entities are reference entity that does not create a replica itself that is why linked entities should not use incremental refresh if they reference a dataflow.
Premium features of dataflows - Power BI | Microsoft Docs
I think there's been a misunderstanding. We're not referring to incremental refresh on linked entities, but for computed entities. See the original post. Thanks!
