How to update dataflow M scripts from JSON file?

[Anonymous]

Hi,

I have created a dataflow in a developer workspace, then exported the dataflow as a JSON file and imported the dataflow from the JSON file into a production workspace, all successfully. Then I have made changes to the M code of the dataflow in the dev workspace. Now I want to export the JSON file from dev workspace and update the dataflow in prod workspace with the changed M code from the JSON file.

Is there a way to update an existing dataflow from a JSON file instead of creating a new dataflow from the JSON file?

The relevant difference is that if I delete the prod dataflow and import the JSON file as new, I would have to change all the datasets depending on the old dataflow to load from the new dataflow ID, which I want to avoid.

Thank you very much!

BR

Martin

[Poojara_D12]

Hi 

Currently, Power BI does not provide a direct method to update an existing dataflow in a workspace using a JSON file without creating a new dataflow. When you export a dataflow as a JSON file and then import it into another workspace, it creates a new dataflow with a new ID, even if the name is the same. This means that datasets or reports connected to the original dataflow will not automatically switch to the new one, leading to broken links unless they are manually repointed. Unfortunately, Power BI does not support updating or overwriting an existing dataflow via JSON import in a way that retains the original dataflow ID. To work around this, you would need to manually update the M code within the existing dataflow in the production workspace using the Power BI Service interface or through the Power BI REST API (if supported), thereby preserving the original dataflow ID and avoiding the need to rebind dependent datasets.

[FADAVI]

Hi, 

I know it is an old post, it seems it's still impossible to overwrite a DF with a JSON template. 

There is a little tip to help:
In your queries which use the DF connector you can change the navigation steps in order to mention the dataflowName instead of the dataflowId.
Example:

let
   Source = PowerBI.Dataflows([]),
   WS = Source{[workspaceName="your_workspace_name"]}[Data],
   DF = WS{[dataflowName="your_dataflow_name"]}[Data]
in
   DF

If you do that you can delete the old DF and import the JSON file with the updated version. You will not have to modify the queries wich mention this DF.

Florian 

[Anonymous]

The idea is already there: Microsoft Idea  · Ability to override existing dataflow with JSON Model (powerbi.com)

[v-kkf-msft]

Hi @Anonymous ,

After testing, I think you can try to directly copy the updated M code in development workspace to the Advanced editor of the dataflow in production workspace. That will update an existing dataflow from a JSON file instead of creating a new dataflow from the JSON file.

If the problem is still not resolved, please provide detailed error information or the expected result you expect. Let me know immediately, looking forward to your reply.

Best Regards,
Winniz

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi @v-kkf-msft ,
Thank you for the support. This is actually what I currently do. But since I have multiple queries that I want to update in the dataflow, this is way more effort than importing all changes from one JSON file at once.

Do you know whether changing the M code of the queries in the dataflow can be automated through Power BI API with Pro or Premium per User license?

Best regards,
Martin 

[v-kkf-msft]

Hi @Anonymous ,

Unfortunately, according to the document https://docs.microsoft.com/en-us/rest/api/power-bi/dataflows , it should be impossible to use Rest API to automatically update the M code.

Best Regards,
Winniz

[dbeavon3]

@v-kkf-msft this is not correct.  There is a REST api that updates the M/PQ code for dataflows.  It is part of the "imports" API.  It doesn't work very well, and is pretty buggy.  But it is there.

[Anonymous]

Hi @v-kkf-msft ,

Thank you! This confirms my research. It seems the API doesn't know anything like a "Query" object in a dataflow, only dataflow level settings affecting all queries. I'll submit the JSON update as an idea.
BR
Martin