Resolve the dependency between multiple solutions in D365 Customer Engagement / CRM Solution using Solution Component Mover.

You have might question in your mind that why we need to move the components from one solution to another solution in D365 Customer Engagement

So, let's consider a scenario you and your team is working on D365 CRM customization and created the two solution — ‘ Solution A’ and ‘Solution B’. While customization development when you are moving the ‘Solution A’ on the Production instance but you are not able to move it. Because some of the missing components are present in the ‘Solution B’.

Then you have decided to move the ‘Solution B’ first, but again while moving the ‘Solution B’ its failed because of some of the missing components present in ‘Solution A’.

It means ‘Solution A’ and ‘Solution B’ are dependent on each other and you can’t move either of the solutions in the Production Environment or Target Environment.

There are two solutions to the above problem

1. Add the missing components in the one solution and move that solution to production.
2. Merge the dependent solution into one solution using Solution Component Mover.

Now, the First solution is time-consuming as well as effort making and developers need to track all the missing components and add them manually.