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?
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
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
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?
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/
Clear, Concise and therefore brilliant - many thanks
thank you, this is exactly what i was looking for with respect to creating a pipeline and configuring environmental parameters.
Pipelines have recently changed so I probably need to redo this one
Very simple explanation on the steps for deployment. Thank you!!!
Glad it was helpful!
Thank you so much for such a detailed explanation. Awesome!
Thank U
this is the best Pipeline explaination for power bi vid
Awesome and simple, Laura! Thanks for sharing!
Thanks will use tomorrow especially the tip to set parameters as Text.
Glad it was helpful!
Explained in a very simple way. Informative videos :)
Awesome and simple!!!!
Amazing Video, thanks!
It's help me a lot! Thank you!
Thanks for sharing.
Excellent, thanks for sharing
many thanks for the share
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?
Yes that does make sense.
Given its SQL server so the queries should fold I'm not sure if that makes it more efficient
@@HatFullOfData123 development-wise it's fewer clicks and that's already something! I use this approach also for SharePoint
This is so precise. Very good. I just subscribed. :)
Great to hear
If we have three different servers for dev,test,prod then how to give those different credentials to different environment in the deployment pipelines
Great explanation Laura, thank you! How would you manage a split report in dataset and thin report?
I think that should work fine as long as the dataset and the thin report are in the same workspace.
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
There is more data in the test database than in the dev one. Same for prod.
Useful... Video
Is this for premium only? Option available for pro?
The dev and text workspaces have to be premium or premium per user. Thankfully premium per user is more affordable for users.
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
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?
Can't we make dynamic instead of doing it manually..?
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/