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)

Managed or Unmanaged? - In-house use only

(0) ShareShare
ReportReport
Posted on by 210

Hi,

I am looking for advice with Managed/Unmanaged Solutions, and from what I understand, the fundamental difference is the ability to make changes after an Export. This seems to only affect Solutions which are to be sold or used in a developer/client scenario, with the developer wishing to ‘Lock’ the solution to prevent changes.

In my case, it's not necessary to 'lock down' the Solution as the solution will not be sold, or used by any external bodies and so making this a Managed Solution for data/copyright purposes isn’t important. Also, customization privileges will be grated using the ‘User Permissions’ to prevent users making changes.

It is however very important to be able to 'Roll back' quickly and easily to the previous Solution, should there be any problems with the most recent import of the solution. Also, the ability to delete any customizations. Is this possible with Unmanaged Solutions? Are there any other considerations?

Many thanks in advance,

Ian

*This post is locked for comments

I have the same question (0)
  • Joe Gill Profile Picture
    on at

    Hi Ian,

    I would suggest that you use managed solution even for a simple environment. Unmanaged solutions simply contain pointers to customizations in the default solution.

    Using managed solutions will allow you to package up your customizations within a solution that can be rolled back easily. As you mentioned you can use managed properties to allow your user to make changes on top of your solution.

    hth

    Joe

  • SyedHussain Profile Picture
    1,820 on at

    Managed/Unmanaged solutions are not just reserved for developers or the sale of a solution. It's good practice to use both depending on your business scenario.

    If your first solution (the one you talk of) is rock solid and you aren't going to do any development work for it anymore, then you can export as a managed solution. This way, you can roll-back changes as you described. If you then want to add new customisation on top of what you already have, you can't add any customisations to that solution because it's obviously locked, but what you can do is create a new solution (call it tier-2 or something similar) and customise in that. All your previous customisations will be fine and you can build more in the new solution (tier-2). Bare in mind that if you need to import the system to another machine, you'll have to include both solutions.

    My advice to you from experience is to keep a copy of both; Managed and Unmanaged in a safe location. This is because if you face a problem in the future, such as upgrading from one platform to another, or upgrading the CRM from CRM 2011 to CRM 2014, you might come across errors or problems that need the solution dissected and fixed before import. Otherwise import will fail.

    Let me know if any of this makes sense.

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!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock 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