Skip to content
Tutorials Center
My learning

Topics

Lesson 28 of 38 ยท Components and ALM

Solutions and Environments

Learn Power Platform environments (dev, test, prod) and solutions (managed vs unmanaged, publishers, layers) so your apps move safely between environments.

A hobby app can live in your default environment forever. A business app needs a safe place to change it, a place to test it and a protected place where users run it. Environments and solutions give you that separation. Together they form the base of application lifecycle management (ALM) on the Power Platform.

Environments

An environment is a container for apps, flows, tables and data, with its own security and its own Dataverse database (optional for some types). You manage them in the Power Platform admin center (admin.powerplatform.microsoft.com), under Manage, Environments.

Common types:

  • Default: created for every tenant; everyone in the organization can make things in it. Not recommended for production apps.
  • Production: for live apps; controlled access.
  • Sandbox: for development and testing; can be reset or copied.
  • Developer: a personal environment for one maker.
  • Trial: temporary.
  • Dataverse for Teams: lightweight, attached to a Microsoft Teams team.

A typical set is Dev, Test (or UAT) and Prod. Each environment is also a region and can belong to an environment group for shared governance rules (Data Loss Prevention Policies).

A common environment path

Dev Build and change
Test Check with real users
Prod Live and protected

Solutions travel left to right.

1 / 2

What a solution is

A solution is a package of components: apps, flows, tables, columns, custom connectors, environment variables, connection references, security roles, charts, dashboards and more. Building inside a solution is the only way to move work between environments reliably.

Create one in the maker portal: Solutions, New solution. You set:

  • Display name and Name (the unique name).
  • Publisher: who owns it. The publisher sets a prefix (for example ct) that begins every table and column logical name (ct_equipment). Make your own publisher; do not use the default one, so your components are clearly yours.
  • Version: major.minor.build.revision.

Then Add existing (existing items) or New (create items inside the solution). Always create new things from within the solution so they are included automatically.

Managed and unmanaged

  • Unmanaged solutions are for development. You can edit every component, and removing the solution leaves the components behind.
  • Managed solutions are what you install in test and production. Components are locked (can be customized only through layering), and removing the solution removes the components.

The flow: develop in an unmanaged solution in Dev, export as managed, and import the managed file into Test and Prod. Never develop directly in production.

Layers

Dataverse stacks customizations in layers: system layer, then managed solutions in install order, then the unmanaged layer at the top. An edit made in the unmanaged layer of production hides later managed updates for that component, a classic source of "my update did not change anything". Check Solution layers on a component (in the component's menu, Advanced, See solution layers) to see who wins.

A layer resolution stand-in

The "top layer wins" rule can be modelled. This stand-in picks the active value of a setting from a stack of layers.

JS Stand-in: which layer wins?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

If you remove the unmanaged hotfix layer, title returns to the managed value. That is why production should have no unmanaged layer.

Solution checks and dependencies

Components depend on each other (a form needs its table). When you export, the platform lists missing dependencies: components your solution needs but does not include. Fix them by adding the components or by making sure the target environment already has them (for example another managed solution). Use Solution checker (in the solution's menu, Solution checker, Run) to catch performance, security and upgrade issues before exporting.

A dependency check stand-in

JS Stand-in: find missing dependencies

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Export and import steps

  1. In Dev, open the solution, choose Export (select Managed and set a new version number).
  2. In Test, open Solutions, choose Import solution, upload the zip, and map connection references and environment variables when prompted (Environment Variables and Connection References).
  3. After testing, repeat the import in Prod.

Automating this with pipelines is covered in Pipelines, Source Control and the CLI.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which type of solution do you import into production?

    Managed solutions are locked and removable as a unit, which suits test and production.
  2. 2. What does a publisher's prefix do?

    The prefix (for example ct_) makes names unique to your publisher.
  3. 3. Why should you avoid editing a managed component directly in production?

    An unmanaged customization wins over lower managed layers.
  4. 4. What should you always do when creating a new component?

    Components created inside the solution are included automatically.

Summary

  • Environments separate Dev, Test and Prod; avoid building production apps in the Default environment.
  • Solutions package components with a publisher prefix and version.
  • Develop unmanaged, deploy managed, and watch solution layers.
  • Run Solution checker and resolve missing dependencies before export.

Next: Pipelines, Source Control and the CLI