Right now if you link an entity to a dataflow in a different workspace, it does not auto-refresh like a linked entity in the same workspace. While this could be advantageous in some situation (for example linking to live data and using the linked dataflow to make "official" snapshots), it could also allow data to become stale. It would be good to allow users to select if a dataflow should stay in sync across workspaces, as well as being able to break the auto-refresh on in-workspace links.
6 Comments
- Completely agree with this. I would be beneficial if it is simply a setting in a dataflow whether or not you want it to be auto triggered if the upstream dataflow gets refreshed. If it is just an option in the dataflow settings, you can decide for every case separately if you want it to be triggered or not, to be more flexible and match multiple scenarios.
- Yes, more orchestration options for Dataflows :)
- Even with low vote count - hope / trust this is on the roadmap already
HI,I will add also the possibility to trigger the dataset refresh as an option when a dataflow is used as a data source.
The linked refresh behaviour leads to data in a transformation dataflow getting out of sync if there are two parallell staging dataflows (which is a common setup). I really wish there was an option to disable linked refresh. https://community.fabric.microsoft.com/t5/Service/Dataflows-Linked-entities-refresh-issue/m-p/4153007
- Status added:Needs Votes
