Solution Layering Issue

In certain customisation scenarios the configuration of the solution layering order can become undesirable.

This occurs because a part of the system was customised via managed solution prior to an Altus update being delivered. When the Altus update is applied to the environment both the managed custom layer and the Altus layer both have the same direct dependency information, so Dynamics chooses to have the most recently deployed solution take the top layer position, and supersedes the user experience.

Solution Approach - Layer Rename

In order to move the Partner customisation layer to the top a solution a renaming approach can be used as per page 35 of the Microsoft Dynamics Solution Lifecycle Management whitepaper.

In this approach, the managed layer that needs precedence is renamed, forcing Dynamics to re-evaluate the layer order.

Step 1

Switch to the DEV environment where the Partner layer is authored. This environment will contain the Partner layer as an unmanaged solution, and due to it being unmanaged, this layer will always appear on the top. Verify that the latest Altus updates have been applied (to the same level as the PROD environment) and the the desired layering order is in place.

Step 2

Extract & Rename

Export the Partner solution as an unmanaged solution.

Keep a backup of this file
Unzip the solution ZIP file
Edit the solution.xml and modify the UniqueName of the solution to ensure it is different to the currently deployed unmanaged solution.

Re-zip the solution into a new ZIP ensuring the pathing inside the ZIP file remains the same as the original

Step 3

Import the modified unmanaged solution file back into the DEV environment. Both unmanaged solutions should be visible

Step 4

Delete the original unmanaged solution from the DEV environment.

Note

Since these are unmanaged solutions, deleting them does not delete any contained entities - and you have a backup of the solution file if you ever need it back.