Solution Management
Customizations
- At least one solution per project must be created and all customizations must be part of this unmanaged solution.
- The following solution components must be included in a separete solution:
- Cloud Flows: Separate solution with
Flowssuffix. E.g.:ITSM365Flows. - E-mail Templates: Separate solution with
EmailTemplatessuffix. E.g.:ITSM365EmailTemplates.
- Cloud Flows: Separate solution with
- Always use segmented solutions! When adding an existing table to a solution, you should only add those components that you wish to customize! Never include all components unless required!
Change Management
Usage of patches
Patch solutions can be used to deploy small changes between environments without having to do a complete solution deployment. However, when a patch is created for a solution, the parent solution automatically becomes locked, exporting the parent solution is prohibited, thus making customizations more difficult and the CI/CD pipelines unable to work properly.
Patching strategy to be defined 🔥
When to clone a solution
When you clone an unmanaged solution, the original solution and all patches related to the solution are rolled up into a newly created version of the original solution. After cloning, the new solution version contains the original entities plus any components or entities that are added in a patch.
Refer to Power Platform Solution ALM article for further details.
Patching strategy to be defined 🔥