Solution Layering in Dynamics 365 CE / CRM / Dataverse (Managed vs Unmanaged Explained)

Solution layering is one of the most misunderstood concepts in Dynamics 365 CE / CRM / Dataverse. Many production issues happen because architects and developers don’t fully understand which customization “wins” when multiple solutions modify the same component.

This blog explains solution layering in a simple and practical way.

---

✅ What is Solution Layering?

Solution layering means:

When multiple solutions modify the same component (form, field, view, etc.), Dataverse decides which customization is applied based on the solution layer order.

Every customization sits on a “layer”.

---

🔥 Types of Layers in D365

There are two major types:

1. Unmanaged Layer

• Created when you customize directly in the environment
• Highest priority (usually overrides managed)

2. Managed Layer

• Created when you import a managed solution
• Multiple managed solutions can stack on each other

📌 Architect Callout:
Unmanaged layer is like “local override”.

---

✅ Layer Priority Rule (Most Important Concept)

The order of application is:

Unmanaged Customizations (Top Priority)
⬇
Managed Solutions (Latest Imported Wins)
⬇
System/Default Layer (Base)

So:

• The most recently imported managed solution will override older managed solutions.
• Any unmanaged change will override managed layers.

---

📌 Simple Layering Example

If 3 solutions modify the same form:

Layer Order	Solution
Highest	Unmanaged Customization
Middle	Managed Solution v2
Lower	Managed Solution v1
Base	System Default

Result:
✅ The system uses the top-most layer customization.

---

⚠️ Why Layering Creates Problems in Production

Common real-world issues:

• A form change is deployed but doesn’t appear
• A field behaves differently than expected
• A business rule seems overwritten

Usually the reason is:
👉 Another managed solution or unmanaged customization is overriding it.

---

🛠️ How to Check Solution Layers

You can check solution layers by:

• Opening the component (field/form/view)
• Selecting Solution Layers
• Viewing which solution is controlling it

💡 Best Practice:
Always check solution layers when troubleshooting missing changes.

---

✅ Architect Best Practices for Layering

Follow these rules:

• Avoid unmanaged changes in Production
• Keep solution ownership clear (one team owns one module)
• Import solutions in correct order
• Use patch solutions only for short-term fixes
• Clean unmanaged layers by moving changes into managed releases

---

Conclusion

Solution layering defines which customization is active in Dataverse. Managed solutions stack, unmanaged overrides everything, and the latest import usually wins. Architects must control layering to avoid production conflicts and upgrade failures.

---