Forum Discussion
How use Deployment Pipelines with Dataflows in Power BI?
For dataflows and datasets that are managed in the same pipeline, the pipeline automatically changes the connections so that Dev dataset will connect to dev dataflow, and Test dataset will connect to Test dataflow. You can also control that yourself through parameters and parameter rules, which requires the user to configure it once.
But if you just want it to work that dev points to dev, and test points to test, it will just work.
Hi,
Thank you for your quick response.
We did a lot of tests. Datasets are always linked to dev dataflows after deploy. Because, in the m query there's the ids of workspaces and dataflows...
- Nimrod_Shalit4 years ago
Power BI Team
If datasets and dataflows are in the same pipeline and workspace/ stage,
when they are deployed they will reconnect in Test/ Prod stages.
If they are not in the same pipeline, then today we don't have a good solution for that yet, but we are working on it- Deployment pipelines - multiple pipelines working together | Microsoft Docs
- Al3454 years agoFrequent Visitor
I have had the same experience as @ptacquet. I have one deployment pipeline with a dev, test, and production stage. When I create something in dev and deploy it to test, the dataflow still references the dev DSN (we use an ODBC connection with a DSN to connect to an AWS instance). I can go in and manually update the DSN in the test workspace but if I deploy from dev again it will be overwritten with the dev DSN.
The real issue here is that when I deploy a report that pulls from the dev dataflow, it doesn't seem to keep a connection to any dataflow. When I download the report and go to the advanced editor, there are no queries in the queries pane.
- Nimrod_Shalit4 years ago
Power BI Team
It's two separate issues:
for dataflow-->datasource connection, you should configure rules on the dataflow to make sure you are pointing to you Test/Prod data source respectively. it can be done directly on the data source, or by using parameters.
As for the dataset-->dataflow connection, it sounds like a bug. this shuold be automatically changed by the pipeline. please open a support ticket.