How to Delete Keys from a Managed Solution Without an Unmanaged Version

Understanding the Challenge

When working with Dynamics 365, you might encounter a situation where you need to remove a key (primary or alternate) from a managed solution. The typical approach involves modifying the unmanaged solution, making the desired changes, and then re-importing it as a managed solution. However, this straightforward method isn't feasible when you don't have access to the original unmanaged solution.

You may encounter this error when attempting to delete keys from a managed solution.        

he "Holding Solution" Technique

A clever workaround, known as the "holding solution" technique, can be employed to achieve this. Here's a step-by-step guide:

Create a New Unmanaged Solution:

• In your target environment, create a new unmanaged solution.
• Add all the components from the managed solution that you want to retain, excluding the key you wish to remove.

Import the Holding Solution:

• Import the newly created unmanaged solution into your target environment.

Delete the Original Managed Solution:

• Carefully delete the original managed solution that contains the unwanted key.

Key Considerations and Cautions:

• Data Integrity: Ensure that deleting the managed solution won't compromise your data. If the key is critical to data integrity, consider alternative approaches or consult with a Microsoft Dynamics 365 expert.
• Solution Dependencies: Be aware of any dependencies that the managed solution might have on other solutions or customizations. Deleting the solution could potentially impact these dependencies.
• Backup and Recovery: Before proceeding with any modifications, create a complete backup of your environment. This will allow you to restore your system to its previous state if necessary.
• Testing: Thoroughly test your environment after making changes to ensure that everything functions as expected.