Removes all custom entities and components contained within the solution.The removal of a Managed solution will do three things: While every environment and situation will obviously contain its own unique characteristics, the following outline This option assumes you have a separate development environment used to build the customizations where the unmanaged solution can be obtained. The option we will explore is the option of deleting the managed solution, and then reimporting an unmanaged version of the same components. There are a couple of different options you could potentially choose in order to deal with this type of scenario. So what do you do if you configured your CRM base solution as a managed solution and you want to change it to an unmanaged version? Also, maintaining a managed solution requires that you preserve an unmanaged copy of that solution somewhere, since that is the only way you can update the solution or delete components.įor these reasons, I recommend that most CRM environments use unmanaged solutions for their internal base customizations. Even in highly secure environments, there are typically some level of customization changes that need to be made in a CRM productionĮnvironment, such as view, chart, and dashboard changes. Managed solutions are great for Independent Software Vendors (ISV’s) who are selling their intellectual property and don’t want it to be modifiedīy their customers, but for internal customization of your base CRM solution, managed solutions can cause some challenges. I typically recommends that users deploying internal customization changes should do so using unmanaged solutions. In CRM 2011, there are two types of solutions: Managed solutions, which prevent the solution fromīeing modified in the environment to which it is imported, and unmanaged solutions, which allow for the solution to be modified after it is imported.
Microsoft Dynamics CRM 2011 introduced the concept of solution management-packaging your customizations so they could easily be deployed to other environments.
0 kommentar(er)
