Using Power Apps Solution Packager to Move Apps to New Environments

Did you know that you can package a Power Apps solution for distribution to another environment or an external customer? There are two ways to do this. One way is to export and import applications, the other is by building a Power Apps solution.

Watch this video to learn how to move apps to a new environment with a Power Apps solution. The benefit of doing it this way is that it packages up a lot of the Common Data Services (CDS) entities and other pieces that Power Apps imports and exports don’t do.

In this video you’ll learn:

• How to use Power Apps solutions and publishers to package a CDS set of objects and apps to a new environment.
• How to create a simple solution, create your entities and app inside the solution.
• How to package up that solution and import it.
• In addition, you will learn about the difference between managed and unmanaged solutions used in the solution packager.

Solutions give you a better application lifecycle management system for integration things like DevOps and source control. It gives you a more packaged way of migrating objects from CDS and Flow and applications from development to QA to production as well as outside your environment to another solution.

Check out my video below for where I’ll walk you through this process.

Having the ability to move Power Apps applications and Common Data Services objects with a solution can be incredibly useful. Be sure to subscribe to our YouTube channel for lots of free Power Apps training. At Pragmatic Works we have plenty of other Power Apps training opportunities. We also can build apps for you, with our Shared Development offerings. Visit our website for more information or click the link below.