Power BI - Create a Pipeline

A video showing how to create a pipeline to deploy a report from a development workspace to test workspace and then onto a production workspace. It requires a premium per user licence or a premium capacity. The example shown uses a SQL Server data source.
Table of Contents:
00:00 - Introduction
00:19 - Add Parameters
03:40 - Publish Report to Dev Workspace
05:10 - Create Pipeline
06:38 - Create Deployment Rules
11:35 - Pipeline Access

[@abelgonzalez3640]

Thank you so much for such a detailed explanation. Awesome!

[@stevehamann9624]

Thank U
this is the best Pipeline explaination for power bi vid

[@kirillperian]

Awesome and simple, Laura! Thanks for sharing!

[@osPA78]

Very simple explanation on the steps for deployment. Thank you!!!

[@HatFullOfData123]

Glad it was helpful!

[@DigiManako]

Explained in a very simple way. Informative videos :)

[@sheasafarnezhad4178]

Amazing Video, thanks!

[@unnikrishnansanthosh]

Excellent, thanks for sharing

[@Milhouse77BS]

Thanks will use tomorrow especially the tip to set parameters as Text.

[@HatFullOfData123]

Glad it was helpful!

[@peperazo]

Awesome and simple!!!!

[@andersonbragherolli9763]

It's help me a lot! Thank you!

[@ashoknxt]

Thanks for sharing.

[@ravitejak9414]

If we have three different servers for dev,test,prod then how to give those different credentials to different environment in the deployment pipelines

[@djenral6153]

many thanks for the share

[@joyishu9662]

Useful... Video

[@emach4392]

This is so precise. Very good. I just subscribed. :)

[@HatFullOfData123]

Great to hear

[@Fernando_Calero]

Great explanation Laura, thank you! How would you manage a split report in dataset and thin report?

[@HatFullOfData123]

I think that should work fine as long as the dataset and the thin report are in the same workspace.

[@AgulloBernat]

If you have to pull many tables from the same database I would leave the query after the step in which you connect, unmark load to the model and base my other queries on this one. Does it make sense?

[@HatFullOfData123]

Yes that does make sense.
Given its SQL server so the queries should fold I'm not sure if that makes it more efficient

[@AgulloBernat]

@@HatFullOfData123 development-wise it's fewer clicks and that's already something! I use this approach also for SharePoint

[@enochbishop8298]

Hi FullHatOfData, Why did the reports show an increase in Test over Dev, and then another increase in Prod over Test regarding the # of Customers? Are records being duplicated? Not sure why the records are increasing per your example? Thank you

[@HatFullOfData123]

There is more data in the test database than in the dev one. Same for prod.

[@bharathipolireddy3890]

Is it possible to have different loading methods (import, direct query) for dev, test, prod. for example I wanted to use import mode in dev , direct query in test, direct query in prod

[@HatFullOfData123]

You can have parameters but I can't think of a way to cleanly paramaterise that. You could have a parameter of limiting the number of rows loaded in dev so making direct lighter and quicker.
What are you wanting to achieve by using import in dev?

[@nayeem3905]

Is this for premium only? Option available for pro?

[@HatFullOfData123]

The dev and text workspaces have to be premium or premium per user. Thankfully premium per user is more affordable for users.

[@siddheshamrutkar8684]

Can't we make dynamic instead of doing it manually..?

[@HatFullOfData123]

There are a number of options.
There is a Rest API docs.microsoft.com/en-us/rest/api/power-bi/pipelines
I've used Macaw's DevOps extension and this blog post data-marc.com/2021/06/04/integrate-power-bi-deployment-pipelines-with-azure-devops/