web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

How to remove components from managed solution deployed on production system.

(0) ShareShare
ReportReport
Posted on by 6

Hello All,

How to remove components from managed solution deployed on production system.

I am having online 2016 system.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Pranesh M Juwale Profile Picture
    1,196 on at

    Hi,

    there is no supported way but

    you can refer : community.dynamics.com/.../how-to-delete-an-old-component-from-your-managed-solution-in-crm-2011-2013

  • Suggested answer
    razdynamics Profile Picture
    17,308 User Group Leader on at

    Hi Octa

    Solutions are Additive so Only by uninstalling the Managed Solution can you remove the components, however one technique is  to Update a Managed Solution for removing a customisation a Temporary solution is required;

    Create a temporary managed solution for the customisations you want to keep using the same publisher, but with a Unique Name. This is so it contains the customised components at a separate managed layer.

    xrm toolbox will be able to copy all the components for you , eliminating risk of missing any components Import it on top of your existing managed solution

    Delete the older managed solution

    This deletes the unwanted managed components while the “holding” solution prevents the wanted customisations from being deleted

    During the delete process, the CRM server finds anything that's from the same publisher and effectively says “dont delete because another solution from the same publisher claims you too." 

    Import the new version of the managed solution

    Delete “holding” managed solution

    The contents are the same, but in two managed layers.  You delete the holding solution after the new version of the solution, While you could eliminate the last two steps, you would have to accept the change in UniqueName of the new solution what's really a new version of an existing solution.  This will allow you to keep your Managed customisations without the data and customisations you want to keep

    To prevent getting in this scenario its always worth performing a good design that is future proof, ie using Lookups instead of Picklists, Name Conventions etc

    Best Wishes, Raz

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans