M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Solution layers

Concept

The component-level stacking of definitions in Dataverse, with a system layer at the bottom, managed solution layers above it and a single unmanaged layer; the top layer usually determines runtime behavior.

✦ CONCEPTSolution layersM365.FM
Title graphic: Solution layers (Concept)

Also discussed

Episodes about Solution layers also cover Dependency analysis, GitHub Actions, Microsoft Lists, Model-driven app, Managed and unmanaged solutions and Default environment (Power Platform).

Description

Solution layers are the component-level stacking of definitions in Dataverse. Each component, such as a table, form or app element, can be defined in more than one place, and Dataverse keeps those definitions in an ordered stack instead of replacing one with another. At the bottom sits the system layer. Above it come managed solution layers, and on top there is a single unmanaged layer. In general, the top layer determines how a component behaves at runtime, which is why the concept matters whenever a change seems to have no effect in an environment.

The stack is built per component, not per solution. Two managed solutions that touch the same component each contribute a layer, and the order in which they were applied affects what the environment ends up using. Edits made directly in an environment, outside a managed package, land in the unmanaged layer and sit above everything beneath them. Because that unmanaged layer is one layer rather than a history of changes, a direct edit can override what a managed solution delivers without any visible deployment step.

This behavior ties solution layers closely to managed and unmanaged solutions. The episode "Power Platform Solutions - Simply Explained" lists managed and unmanaged as the two modes of a solution and covers solution layers as a topic of their own next to publishers, prefixes, dependencies and moving an app between environments. Together these explain why a component can look different in development than in a downstream environment, and why removing something can be blocked by what depends on it.

The practical decisions around solution layers concern what is deployed into which environment. The episode "Deploy Dynamics 365 Customizations with ALM Pipelines" names deploying unmanaged solutions into UAT or Production for quick fixes as a common mistake that can lead to long-term chaos and painful troubleshooting. Its advice is to use managed solutions for production environments and to check the Solution Layers view before every release. Reviewing the layers of a component shows which solution currently defines it and whether an unmanaged customization is sitting on top of it.

Solution layers also appear as a design device and as a cost of complexity. The episode "Microsoft Dataverse as a Business Data Backbone" describes standing up solution layers named Core, Extensions and App as part of application lifecycle management, structuring customizations so that foundation, additions and the application itself are kept apart. The episode "SharePoint Lists vs Model-Driven Apps: Avoid Overbuilding" lists solution layers among the things that Dataverse brings along, together with licensing, security matrices, environment sprawl and governance latency. It argues that for simple needs these overheads can outweigh the benefit, so the layering model is worth taking on only when the scenario actually calls for Dataverse.

In short, solution layers describe where a component's definition comes from and which definition wins. Knowing the order of system, managed and unmanaged layers helps with troubleshooting unexpected behavior after a deployment, with keeping production environments clean, and with planning how customizations are packaged across environments.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Key points about Solution layers

Key points about Solution layers from the episodes, each with its source episode:

Episodes about Solution layers

Episodes in which Solution layers is discussed:

Timeline of episodes about Solution layers

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What are solution layers in Dataverse? (AI)

They are the component-level stacking of definitions in Dataverse: a system layer at the bottom, managed solution layers above it and a single unmanaged layer on top. The top layer usually determines runtime behavior.

Why should the Solution Layers view be checked before a release? (AI)

The episode "Deploy Dynamics 365 Customizations with ALM Pipelines" recommends checking it before every release. It helps reveal which solution defines a component and whether an unmanaged change is overriding it.

How do solution layers relate to managed and unmanaged solutions? (AI)

Managed solutions form the layers above the system layer, while changes made directly in an environment go into the single unmanaged layer on top. The episode advises using managed solutions for production environments.

When is a model-driven app overkill?

When the problem only needed a shared list and a few notifications. Dataverse adds licensing, security matrices, solution layers and environment sprawl that slow delivery. · From the episode: SharePoint Lists vs Model-Driven Apps: Avoid Overbuilding

What hidden costs does Dataverse bring?

Dataverse drags licensing, security matrices, solution layers, environment sprawl and governance latency into the project. Teams then spend their time on schema tweaks, role puzzles and dashboards nobody opens, instead of solving the original problem. · From the episode: SharePoint Lists vs Model-Driven Apps: Avoid Overbuilding

What is the Solution Layers view used for?

It shows how solution layers stack in an environment, so you can spot conflicts before a release. The episode recommends checking it before every release to align layers and avoid surprises after deployment. · From the episode: Deploy Dynamics 365 Customizations with ALM Pipelines

What are managed and unmanaged solutions?

Managed and unmanaged are the two modes of a solution. Together with publishers, prefixes and solution layers, they decide how a solution moves between environments and what can be removed. · From the episode: Power Platform Solutions - Simply Explained

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: