Solution Life Cycle – D365

Hey there!

This post is in continuation with my previous post where we have seen What are Solutions. In this post, we will learn about Solution Life Cycle.

If you are looking for more videos on Dynamics, please check my YouTube channel here. Subscribe and stay tuned for more.

With the help of solutions, we can maintain the Application Life Cycle Management. Following actions supports application lifecycle process:

1. Create: Create solution and export solution to import it into higher environment.
2. Update: Add updates/customization into the solution and then import it as managed solution to export it into higher environment over the existing/parent managed solution. It will update the solution but deletion of components can’t be done using Update.
3. Upgrade: With solution import as upgrade, unused component can be removed, version will change, components can be deleted. New logic added into solution will also be implemented.
4. Patch: If we want to deliver small hotfixes such as small adding or editing of components then we create patch solution and export it. Once it is imported , it will be layered over the existing/parent managed solution. Components can’t be deleted with patch solution.

Which one to use?

So, we we are creating a solution and added our components into the solution, then we can export it and import it as update for the first time. Now, we have deleted some components from the solution in lower environment then we can export it and import it as upgrade to delete from higher environment as well. Now, we want to do a small change like addition of a new field or any small change and don’t want to import full solution because of a small change, then use patch to import only small change in higher environment. It will create a layer on top of existing parent solution.