welcome to XRM blog

Keep in touch with latest CRM/ERP articles

To remain competitive your organisation must be efficient across the business process spectrum. To do so you need to take sound decisions based on a balance between the cost and risk. To do so you will be heavily dependent on your content management in itself needs...


Microsoft Dynamic CRM Solution

By xrmlabs webmaster on 3/13/2013

 This is tells about Solution in Microsoft Dynamic CRM 2011 and how it works. There are three types solution as system (default) solution, managed solution, unmanaged solution.

Default Solution

In Microsoft Dynamic CRM organization there is a solution that contains solution component that can be customized. Together all this solution component is called as default solution. This solution can be customized by selecting Customize the System same as unmanaged solution. Default solution can be exported as unmanaged but it cannot be export as managed solution.


Unmanaged Solutions

In Dynamic CRM all solutions start as unmanaged solution. This you can say is initial stage or solution where do the following :

  • · Can add, delete, update, and remove the solution component,   managed properties, configuration and the update the publisher of the solution. You can update the version of the solution.
  • · Export and import unmanaged solution.

· Export as unmanaged version as managed solution. 

When all changes has been done in suppose in dev system(organization) then you can export the solution as unmanaged and managed solution to another system or production system (organization). Best practices is that you should export unmanaged solution as managed version from dev to production system because managed solution is not editable and user can made the change final solution in production. When you do import an unmanaged solution, the definition of any components of solution that already are in the organization will be overwritten. You cannot revert this action.

Managed Solutions

When you are done with your unmanaged solution i.e. it is completely done, you can then export solution as managed to production. In managed solution you get restricted to do things like

  • ·Cannot add or delete any solution component. 
  2. ·They cannot be exported.
  3. ·If deleting unmanaged solution, this will uninstall all solution components within it.

After you have generated a managed solution, you cannot install it in the same Dynamics CRM organization that contains the unmanaged solution used to create it. It must be installed in different organization.

After you install a managed solution you may be able to customize the solution components if the builder of the managed solution has configured the managed solution to do so. You must access the customizable solution components using “Customize the System” instead of through the managed solution itself.

To check solution component is customizable and what customization actions are enabled is controlled by using Managed Properties of entity.

** In unmanaged solution Managed properties must be set  and managed property settings are only applied after the managed solution has been packaged and installed.
Once you have final solution as Managed Solution, it can be installed into another organization and also be deployed in multiple deployment types like online, partner hosted, and on-premise.

How solution works to show up in application

As you can see from the figure below show how the unmanaged solution & unmanaged solution interact with system solution to show up in application behaviour. The system (default) solution is overridden by managed solution & which is further overridden by unmanaged solution. Thus whatever is the final result which is seen by the user in application.

 For example if in Dynamic CRM organization (contains system (default) solution) we first add managed solution having custom entity with field named “Client”, then Save & publish. This will overwrite field named as “Client” in default solution. Now if we again add another managed solution having field named as “Individual”, this will overwrite the previous solution customization & field name will change as “Individual” and the final field name will be “Individual” visible to user. This means solution installed last with customization done on same solution component will override the previous customization.

Default Solution
Managed Solution
Unmanaged Solution
Blog Calendar
Blog Calendar List
2018 Nov  22  3
2018 Oct  7  3
2018 Sep  13  11
2018 Aug  2  2
2018 Jun  11  1
2018 Jan  41  2
2017 Sep  348  5
2017 Aug  14  1
2017 Jul  15  2
2017 Jun  36  2
2017 May  17  1
2017 Apr  31  2
2017 Mar  104  4
2017 Feb  269  4
2016 Dec  171  3
2016 Nov  265  8
2016 Oct  197  10
2016 Sep  341  6
2016 Aug  38  1
2016 Jun  1580  6
2016 May  102  3
2016 Jan  68  2
2015 Dec  373  6
2015 Nov  3  1
2015 Oct  11  1
2015 Sep  1104  6
2015 Aug  10  1
2015 Jul  101  2
2015 Jun  7  1
2015 May  20  1
2015 Apr  21  2
2015 Mar  67  3
2015 Jan  4997  4
2014 Dec  14  1
2014 Nov  2159  4
2014 Oct  74  2
2014 Sep  95  2
2014 Aug  2847  1
2014 Jul  40  2
2014 Apr  2401  12
2014 Mar  268  19
2014 Feb  216  8
2014 Jan  1490  16
2013 Dec  21  2
2013 Nov  607  2
2013 Oct  239  3
2013 Sep  10  1
2013 Aug  29  3
2013 Jul  202  1
2013 Apr  43  6
2013 Mar  1633  10
2013 Feb  272  4
2013 Jan  244  2
2012 Nov  24  2
2012 Oct  394  10
Tag Cloud
Interested in our services? Still not sure about project details? get a quote