Using Pipelines to Simplify Power Platform Deployments
Vložit
- čas přidán 19. 10. 2023
- 👉 On-Demand Learning - Start With The FREE Community Plan: prag.works/odl-trial-yt
In this video, we explore how pipelines can simplify your Power Platform deployments. Pipelines are a useful tool that allow you to automate and standardize the deployment process, ensuring that your solutions are deployed consistently and efficiently across environments. We'll cover the key concepts of pipelines, demonstrate how to create a simple pipeline, and show how to use pipelines to deploy a Power Apps solution. Whether you're new to pipelines or an experienced user, this video has something for you. Join us and learn how to streamline your Power Platform deployments today!
👍 If you enjoy this video and are interested in formal training on Microsoft Teams, Power BI, Power Apps, Azure, or other Microsoft products you can visit prag.works/BRIAN40 for 40% off On-Demand Learning!
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - -
Next step on your journey:
🔗Pragmatic Works On-Demand Learning Packages: pragmaticworks.com/pricing/
🔗Pragmatic Works Boot Camps: pragmaticworks.com/boot-camps/
🔗Pragmatic Works Hackathons: pragmaticworks.com/private-tr...
🔗Pragmatic Works Virtual Mentoring: pragmaticworks.com/virtual-me...
🔗Pragmatic Works Enterprise Private Training: pragmaticworks.com/private-tr...
🔗Pragmatic Works Blog: blog.pragmaticworks.com/
Let's connect:
✔️Twitter: / pragmaticworks
✔️Facebook: / pragmaticworks
✔️Instagram: / pragmatic.works
✔️LinkedIn: / pragmaticworks
✔️CZcams: / pragmaticworks
Pragmatic Works
7175 Hwy 17, Suite 2 Fleming Island, FL 32003
Phone: (904) 638-5743
Email: training@pragmaticworks.com
#PragmaticWorks
That's a great introduction video! Thank you, Brian.
Great video! Unfortunately, it sounds like the biggest drawback is that all users need premium to use any of the apps in these environments. If this is accurate, then there's no way this will ever be used with actual businesses. It is rare to find a business that will have all their users licensed with premium as it costs too much. I can understand requiring the account doing the deployment needing premium, but that is about it.
Thank you :) question, is it possible create pipelines for unmanaged environments but managed solutions?
Great video Brian! Thank you!
Nice to learn about. Thank you 😊 👌🏽.
This is great. Thank you, Brian, 😇
Hello, I am new to powerapps, How dev env deployed first before deployed test ?
Great Video! You mentioned the ability to configure approvals on the pipeline. I currently have a Dev --> Test --> Prod pipeline running which is great for source control and deployments. The major downfall I am running into is having to hunt down my test users to verify changes and publish to Prod. Would it be possible to get a video showing how to implement the approvals? something like Dev publish to Test, approvals assigned to the user group of the app, once approval is completed a task is assigned to publish to Prod.
Great idea! 💡I added it to my queue - Brian
Heard about, but never understood pipelines, and now at last the mystery is being cleared up. Thx! So here’s my related follow up question: Let’s say I have a big customer like Ford and they need an accounting app. Would I want to create a new dedicated developer environment called FordAccountingDev and then continue your pipeline steps from there? And if they needed a marketing app would I make an environment called FordMarketingDev within which to build out the pipeline for that marketing app? Or is there a third/simpler way structured around one environment for Ford with perhaps multiple pipelines/solutions etc?
@Brian - thanks for the video... We have customized the process to include approval workflows - but when it comes to Power Automate and Power Apps - this whole pipeline tool has some shortcomings. Trying to share connections and/or connection references, even when using a SPN doesn't seem to work correctly. At what point should someone abandon this and go with Azure DevOps instead?
Thanks for the overview! Very useful. I'm curious how would this work if I want to sell my PowerApp. How do I publish it to my clients environment and/or to the windows apps store (What would you recommend?)
The pipeline feature is isolated to a given tenant so you'd have to do the traditional export / import option for your client. Depending on your customer relationship, you could import unmanaged into their dev and let pipelies take over from there. - Brian
Does solution checker run automatically in the pipeline? Or do I need to do something? I have managed environments so feature itself is there.
Great video Brian!! What happens to the existing solution in production (update / upgrade), Thank you.
There are lots of shortcomings. It just didn't demand the premium license however it also demands Maker access on target environment for the user who is running the pipeline. I can still digest that organization can somehow provide the premium license to users however providing maker right to business is difficult.
One thing missing is the dependencies. every time a new change is made in the source. make sure to include objects from the solution element before deploying. it really took a while to figure than out.
Hi Brian, Thanks for the video. I tried to set up pipeline as per your instructions, but when I create the Dev, UAT, Production environments using the environment Id, I am getting this error "Environment 9e9a7697-9cc9-47d7-8d6c-8655f36404a7 is already configured with Pipelines in host environment 9f0e98b9-addb-e45c-b8a5-921e649f6cc6. Please delete the environment from the other host to add the environment to this host environment 9e9a7697-9cc9-47d7-8d6c-8655f36404a7 or perform a Force Link." I could not find the environment with guid "9f..." would it be OK to use Force link. Another question is our UAT is an Un-managed environment - can we use this pipeline to deploy to Un-managed environment. Though I read everywhere that Pipelines can only be implemented for managed environments.
Do we have apis for these pipelines to automate the deployments
Everyday, there's less and less you can do with a regular license :/
I build my pipeline using the following: Dev (Developer and Managed=yes) to Test (Developer and Managed=yes to Prod (Developer and Managed=yes). I installed the Power Platform Pipeline App in my 'Host' Environment which is a Trial Environment and not Managed. This works fine for learning and testing. My question is this: Is there currently a way to use this kind of pipeline to rollback a solution to a lesser version (other than doing a manual export/import). None of this costs me anything while testing. Thanks.
Are you AI and learning from videos lol. From the discussion I had with Microsoft, once you have deployed a solution, you can only increase the version, or you may have to totally delete the solution. So, effectively, you could increase the version number in solution.xml of the older solution(CurrentdeployedSolutionVersion+1) and use upgrade option to deploy it.
Great video, but as @KyleSchroeder says, its unfortunate that it requires all users to be premium. It would be better either if Microsoft changed that so all users/apps didn't have to be premium, or if the last target in the pipeline didn't have to be a managed environment (even if all interim sources and targets did). We are really struggling with how to best manage our licensing vs. feature sets and Microsoft is not making it easy for those of us who have a combination of premium connected Apps and standard Apps.
I watched the video and proceeded without using Managed Environments or having a Premium License, and it still worked successfully. Could you clarify why you recommended using Managed Environments?
I just retried and it now looks like there's been a slight alteration. The message now states "Target environments must be managed". So it might have let you work this on the source system but when it comes to the targets, they'll all need to be managed. Hope that clarifies . --Brian
@@PragmaticWorks Yeah it was right on the top about the "Target environments must be managed", but even Target worked without making to Managed.