Forum Discussion
Premium P1 Capacity - Dataflows - Corrupt Model
Hi, Anonymous
The error message says that the model.json file cannot be found, which may indicate that the model is corrupted. As mentioned earlier, exporting JSON and creating a new dataflow from it can successfully recreate the dataflow.
However, this results in a new DataflowID, which can cause issues with deployment pipelines and semantic models that rely on the original DataflowID in their M code. You can check the following link:
Power BI Dataflows for Creation of Reusable Data Transformations (mssqltips.com)
There is a way to change the source of a dataflow in Power BI Desktop under Power Query Editor. You can change the source to the new dataflow details, or select a different dataflow option from the list. This may help to switch dependencies to the new DataflowID. You can check link:
Solved: How to Change report built from one dataflow to an... - Microsoft Fabric Community
If you're not the owner of the dataflow, many settings are disabled. To take ownership of your dataflow, you can select Take over to take control.You'll be prompted to provide your credentials to ensure you have the necessary level of access. You can check the following link:
Configure and consume a dataflow - Power BI | Microsoft Learn
How to Get Your Question Answered Quickly
Best Regards
Yongkang Hua
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for your reply and information in the links.
We're still working through the problem with Microsoft support trying to make sure that the DataflowIDs don't change on our Production dataflows as we have a lot of reports (semantic models) that depend on one particular dataflow that has many entities inside it.
One thing I have learnt for new reports, that it is probably worth editing the M-Code to parameterise the Workflows and Dataflow IDs to make it easier to change. For example to switch between Test and Production areas.
Our "corrupted" dataflow is within the Test workspace inside a pipeline. We have tried to re-deploy the dataflow from Development to Test to no avail.
Our next thought is to detach the Test workspace from the pipeline, "rebuild" the broken dataflow by deleting and recreating it (from JSON). Then hoping the Test workspace will successfully attach back into the pipeline.
Would be good to know if anyone has faced a similar scenario before ?