From 748bf45d6d3a857500aeff4d47602a3614642ec0 Mon Sep 17 00:00:00 2001
From: joshuaskipper <130402575+joshuaskipper@users.noreply.github.com>
Date: Sat, 23 Aug 2025 15:07:49 -0400
Subject: [PATCH] Added best practices section to prevent missing dependencies

This change introduces a new "Best practices" section to the article, providing clear guidance for managing solution components and preventing dependency issues.

The current documentation is excellent for troubleshooting. This update builds on that strength by adding preventative guidance, helping developers avoid errors from the start through proper solution design.
---
 .../missing-dependency-on-solution-import.md  | 28 +++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md b/support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md
index 45ee86698f8..3e0580b6172 100644
--- a/support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md
+++ b/support/power-platform/dataverse/working-with-solutions/missing-dependency-on-solution-import.md
@@ -27,6 +27,34 @@ The solution has dependencies on a component that exists in the source environme
 
 This issue might occur when applications are upgraded to the latest version through Microsoft scheduled maintenance in the source environment, but they aren't upgraded in the target environment.
 
+## Best practices to prevent missing dependencies
+
+When creating a new solution in Power Platform, it's often beneficial to reuse existing components rather than building from scratch. This approach promotes consistency and accelerates development. However, there are several important considerations to keep in mind when working with existing objects across environments.
+
+### Ensure component availability in target environments
+
+If you're adding existing components (such as tables, flows, or apps) to a solution, those components must also exist in the target environment when deploying the solution—whether via deployment pipelines or manual import. Failing to do so will result in missing dependency errors during import.
+
+### Select only necessary components
+
+Avoid adding entire tables or components to a solution if you only need a subset of their elements (for example, specific columns, views, or forms). Adding unnecessary elements can lead to:
+
+- Increased solution complexity
+- Multiple managed layers being applied to components
+- Potential conflicts during updates
+
+Instead, selectively include only the parts of the component that your solution actively uses.
+
+### Avoid modifying components in managed solutions
+
+Do not make changes directly to components that are part of a managed solution. Doing so creates an unmanaged layer on top of the managed component. This unmanaged layer can:
+
+- Override updates from the source managed solution
+- Cause inconsistencies across environments
+- Prevent changes (such as updates to Power Automate flows or table configurations) from being reflected correctly after deployment
+
+To ensure smooth deployments and maintain solution integrity, always apply changes within an unmanaged solution or extend functionality using solution layering best practices.
+
 ## Workaround
 
 To work around this issue, follow these steps: