Ability to override existing dataflow with JSON Model

[mariuszrepczyns]

Please can you add an ability to override existing dataflow with JSON Model

[martin_bubenhe1]

I need this too to update dataflow in production workspace with changes that I created in dev workspace. Importing the JSON as new dataflow is not an option because it gets a new dataflow ID, so I would have to change all depending datasets as well.

[Scott_Thomson1]

When migrating to production, we shouldn't be editing/adding table directly in prod. This is very risky. Of course, if the Pipelines get fixed to allow migration of linked dataflows this wouldn't be an issue.

[RBunting1]

One of our dataflows somehow had a new property (Connection Override) that we don't understand how it got there. It was easy enough to remove the property from .json and republish. But now ALL the dependent reports will need to be updated to the new dataflow. Such a pain, the ability to edit-in-place would really have helped.

[mira_nikkila]

This is very much needed - there is no point changing several queries using Advanced editor. If I could update the existing dataflow from json, it would be much quicker and I could be sure, all the content has been updated.

To other users of dataflows - in a dataset, filter based on dataflowName instead of id and you don't have to make any changes in dataset after changes in dataflows.

[rahulvikas_alka]

Not able to add description for already created dataflow. Even when I save it by adding description it disappears. Other way is to update Json by adding description and import it again. However it create a new dataflow by adding postfix as 1 since dataflow with same name is present. Ideally it should ask if we need to overwrite existing dataflow.

[ielizaga]

+1 to this idea, looking forward to seeing more ways to change PBI datasets, queries and dataflows programatically

[denzil_foakes]

Another pretty basic omission from the Power BI experience considering it's been in development for many years. Not being able to overwrite using JSON means a separate workspace can't efficiently be used as a dev area.