Solutions overview

In Power Apps, solutions are leveraged to transport apps and components from one environment to another or to apply a set of customizations to existing apps. A solution can contain one or more apps as well as other components such as site maps, entities, processes, web resources, option sets, and more. You can get a solution from AppSource or from an independent software vendor (ISV).

More information: Solutions concepts


If you’re an ISV creating an app that you will distribute, you’ll need to use solutions. For more information about using solutions, see Developer Guide: Introduction to solutions.


A component represents something that you can potentially customize. Anything that can be included in a solution is a component. To view the components included in a solution, in solution explorer go to Settings > Solutions and then open the solution you want. The components are listed in the Components list. Notice that you can't edit components contained in a managed solution.

Components in solution

To view a list of component types that can be added to any solution, see ComponentType Options.

For more information about solutions, see these articles:

Some components are nested within other components. For example, an entity contains forms, views, charts, fields, entity relationships, messages, and business rules. Each of those components requires an entity to exist. A field can’t exist outside of an entity. We say that the field is dependent on the entity. There are actually twice as many types of components as shown in the preceding list, but most of them are not nested within other components and not visible in the application.

The purpose of having components is to keep track of any limitations on what can be customized using managed properties and all the dependencies so that it can be exported, imported, and (in managed solutions) deleted without leaving anything behind.

Next steps

Use solutions in Power Apps