Here, We will discuss how we can export and import managed and unmanaged solutions and how solutions are combined when multiple solutions are imported into an organization. You will also discover how to use managed solutions to prevent the solution from being customized further. A self-test section at the end of this chapter will test your knowledge.
In coming section we will cover:
A solution is a package of customized components that can be imported into a Microsoft Dynamics CRM 2011 system. Each solution has a name, version number, and publisher who owns the solution. Solutions are used for promoting customizations from one organization to another, or installing customizations provided by a software vendor.
A solution must have a publisher. This is the person, department, or company that develops and publishes the solution. The publisher defines the prefix used for custom entities and fields, and the option value prefix.
A default solution is installed with every CRM 2011 organization. It contains all the system entities.
We can create new solutions. When we create a new solution, it is unmanaged and does not have any solution components. We can either create new solution components or add components from other solutions.
An unmanaged solution’s components are just references that point to components which actually exist in the default solution. When you delete an unmanaged solution, the solution container and its references are deleted but the customizations still exist in the default solution.
The result of deleting a managed solution is different. Unless you have added components from another solution, a managed solution’s components exist in the solution itself. When you delete a managed solution, the solution container and the actual components are irreversibly deleted.
A solution component is a customized element of Microsoft Dynamics CRM. You can create new solution components and add references to components in other solutions.
Solution components can be deleted or removed. When a component is deleted, it is irreversibly deleted from the solution in which it was created. When a component is removed, the reference to the component is removed from your solution but the component still exists in the solution in which it was created.
Usually, the components of a managed solution cannot be customized. However, you can modify the managed properties of your solution’s components before you export the solution as a managed solution to enable components to be further customized according to your requirements.
You can export solutions so that you can promote your published customizations from development to test to production environments or to package customizations for delivery to your customers.
Managed solutions can be customized after being imported into your target organization, but managed solutions cannot (unless you have modified the solution component’s managed properties). You cannot install a managed solution into the same organization from which it was exported.
The merge strategy is applied only to user interface components—ribbons, forms, and views. For user interface components, the merge strategy means that application’s final behavior is calculated from the default solution, then from the managed solutions, and finally from the unmanaged solutions. We can remember
the merge strategy with the following mnemonics:
- Many Urgent Inquiries Don’t Seem to Matter Utterly
- Merge (User Interface) – Default Solution, then Managed, then Unmanaged
The top wins strategy applies to all solution components except user interface components. For these components, the application’s final behavior is calculated from the default solution, then from the managed and unmanaged solutions in the order they were imported. Any conflict is resolved in favor of the customization that was applied last. We can remember the merge strategy with the mnemonic:
- Today Will My Urgent Orders Increase?
- Top Wins – Managed and Unmanaged – by Order Installed
When you install an update to a managed solution, you can choose whether to maintain or overwrite any customizations that you have applied in the unmanaged solutions.
When you import solution, the final step of the solution import wizard will display the results of the import procedure. To help you troubleshoot any issues, you can download the solution import log file, which will provide a more detailed explanation of the error.
This chapter is a part of MB2-866 Microsoft Dynamics CRM 2011 Customization and Configuration Prep course. More chapters in this course are
The Practice tests included in this course are: