Forum Discussion
dataflow permission to access issue
The other user do see the take over sign. However, I need to help set up the standard gateway in order to make it work.
It's been like this since dataflows first hit the streets. They are owned by someone, ONE person. They *should* be owned by the WORKSPACE, so that any admin can edit them with the need to 'take over'. You don't see any Dataset or Dashboard or Report being owned by any ONE person, so why Dataflows?
MS seems to conveniuently ignore this oversight.
<\sigh>
Agreed - it's one of the many oversights of Dataflows.
I love them but they are a pain.
Issues I still see
- I deploy models and dataflows via deployment pipelines. The release management team can pick up the baton and deploy datasets via the deployment pipeline. But cna't do this for dataflows. If they take ownership then there is a danger of losing credentials and DP rules. It also stop me deploying in future!
- You can't look at them via Tabular Editor
- If you use orchestration good like finging dataflow errors when using linked entities. They all succeed or fail and you have to open up everything and see where the issue is
- Gen 1 dataflows are not compatible with source control. Really? At the very least you want to export the json definitiojn
- You can't update a dataflow using a json definition. You have to key in changes manually. So not great for restoring other versions