Applies to: Dynamics 365 with Dataverse

Solution management is the core design tenet of any Dynamics 365 implementation with Dataverse. Medium-to-complete engagements often require multi-solution models where the solutions are horizontally segmented. Implementations of this type involve dividing solutions based on the type of components that they contain (for example, plugins, flows, and PCF controls), to achieve developer isolation. For these projects, it's important that developers adhere to the segmentation. Otherwise, solution layering issues and dependency conflicts can occur that take months to finish fixing and might require support tickets/resolve layering issues.

The Solution component validation tool provides proactive alerts about deviations from the intended horizontal segmentation in solutions. It can help developers, leads, and Azure DevOps teams maintain the agreed-on solution structures for healthy application lifecycle management (ALM). Learn more about solutions and ALM inSolutions overview.

Prerequisites

• Get the samples and tools.

The tool is a managed solution that includes the following components.

Benefits from the tool

• Provides proactive alerts to developers and leads during the development stage
• Saves manual efforts of fixing layering issues on upstream environments
• Helps avoid additional delays because of support requests to resolve layering issues

Installation steps

1. Download the package fromALM.
2. Open the target environment, go toSettings, and then selectSolutions.
3. SelectImport, select the zip file, and then import the solution.

Learn more inImport solutions.

Configuration steps

1. For each solution that you want to monitor, add a newcomponent auto mailer record.

2. Fill in the fields based on the following table.

   Field	Description
   Solution Name	Enter the name of the solution, such asSolution Component Auto Mailer.
   Solution Guid	Enter the ID of the solution. You can get this ID from the URL in the maker portal.
   Allowlist Component Object Code	List, by object type ID, the components that you expect the solution to include. For example, to allow components of theEntity andAttribute types, specify["1","2"], including the square brackets. The report includes all other component types if they are added incorrectly to the solution. Learn more insolutioncomponent EntityType.
   Owner	Use a semicolon-delimited list of email addresses that should receive the report.

The report

The recipients receive an email that shows a list of component types that have been added incorrectly to the environment. The email contains the solution ID and the types and IDs of the relevant objects.

Related content

• Solution layers with Microsoft Power Platform
• Application lifecycle management (ALM) with Microsoft Power Platform
• Application lifecycle management (implementation guide)
• ALM strategy for Dynamics 365 solutions