Update Data Sources within Deployment Pipelines

[@bradj229]

Glad you included the deployment pipeline piggybacking the Power Query parameters and their interaction together. That helped a lot. Thanks!

[@dezcraft_dev]

Works great for semantic models. Hope to see a parameters adjustment feature come soon for Fabric pipelines and notebooks as well. That would open up a lot of opportunities for us from a all up fabric perspective

[@majordisorder]

Starting to use deployment pipelines but don't like that a workspace can only reside in one. Are there any plans to change this as it really restricts our workspace reusage as we can only publish to one ultimate destination.

[@etherlords88]

Thank you, this one helped me big time, realized that pipeline just pipes the code, it's not like copy and replace the old one to the next environment and it does not pass the connection parameters unless instructed as you've shown in the video. This one saved me from deleting the report on the target env which would be a huge pain for me as the dataset is also feeding other reports in my case!

[@guilhermemoura6441]

Great explanation @Adam, what happens if the new source configured on the parameter rules has a different schema. For example if DEV has two more columns than on PROD. It will fail?

[@satellitepop]

Question : What if I have a lakeDEV in a development environment, but my lake in prod is called lakePRD ? And, of course, I have a sampleFile.csv in DEV with 15 Mb. , but I have the same sampleFile.csv in PRD with 15 Gb. So, how can I setup the same Deployment Pipeline changing the name of my Lakehouse and not replacing my file ?

[@jasondenne8153]

Q. I have the same issue. Using Azure ADLS Gen2 connector, and want to point Dev Workspace to Dev Storage and Prod Workspace To Prod storage. Currently this DataSource doesn’t work with Deployment Pipelines , and if you try using parameters then you run into the ‘dynamic data source unable to refresh on service’ issue.

[@Fernando_Calero]

Great video, thanks @Adam. So, we don't have to create a new parameter for the Production database?

[@harshavardhanareddy2436]

Instead of personal cloud how we can configure through gateway connection for dev test prod using deployment rules through pipeline?

[@IvanGordeyev-wk1rp]

Hello, Adam. What about the Direct Lake semantic models? They don't support development pipelines. The only proposed option is to use Git repository integration with multiple branches (dev/prod). But during merging between branches we can't change the lake house. Are there any options?

[@rubininagaraj8071]

Setting datasource rules is not supported for AWS redshift db?

[@kobeathris4552]

Is there a way to use this method with Dataflows as well? I have reports that are direct query to Dataflows, and it seems like if I try to parameterize the dataflow connection, A) its a pain, and B) once I add the parameter, Power BI insists that the table must be converted to import mode.

[@GuillermoArrabal]

This feature is amazing. But I have problems with paginated report visual and power apps visual. When I deploy my report I can't point the visuals to the new environment, any recommendations?

[@buddhigupta3557]

Deployment rules always had issues since start. Every time I had to go back to use Parameters. Further it doesn’t work for Data Pipeline either.

[@kel78v2]

What’s an alternative option to using deployment pipelines?

[@gkirankumarskht]

Hi Adam, I have a question regarding our workspaces. We have already created three different workspaces, and currently, we are manually moving the reports from Dev to UAT to Prod. I want to streamline this process by creating a deployment pipeline using our existing workspaces. However, whenever I try to create a deployment pipeline, it ends up creating another workspace instead of utilizing the existing ones. Could you please provide guidance on how to achieve this? If possible, could you make a video.

[@topher60657]

Can you change the semantic model if you are deploying a live connected report?

[@davidprovost3363]

Good one. When staging my report to prod ws, will it be looking for a semantic model with the same name in prod ws, or still point to the dev semantic model ?

[@GuillermoArrabal]

With SSAS it works perfectly, you can apply the same rules as the video.

[@nakuldeep7336]

when we publish Dev Data to power bi service if anything we want to change in real environment how to change it

[@rahulmaurya9444]

I came across a situation where while deployment instead of replacing the report it's duplicate the report and dashboard

[@mrTonYT987]

first

[@GuillermoArrabal]

This is an amazing feature, but I have problems with paginated report visual and power apps visual. When I deploy my report I can't point the visuals to the new environment, any recommendations?

[@xXDUSC8Xx]

have you been able to figure something out for the paginated report?