- Microsoft Dynamics CRM 2011 Scripting Cookbook
- Nicolae Tarla
- 473字
- 2021-07-27 18:12:37
Using solutions to package our work
A new concept introduced with Dynamics CRM 2011 is that of solution packages. This allows for code separation, ease of deployment, and cleans up the mess sometimes created in previous version by the large number of possibly unorganized customizations.
Getting ready
In order to follow through with this recipe, log in to your instance of Dynamics CRM 2011 with an account that has either an administrator or system customizer role. These roles have the necessary out-of-the-box permission to allow you to work with solutions.
How to do it...
A solution package is a collection of customizations and configurations that can be generated in an environment and relocated to an additional environment. Creating a new solution is a process that a system administrator or a system customizer can achieve with the following steps:
- Navigate to Settings.
- Under Customization, click on Solutions.
- In the All Solutions view, select New to create a new solution package.
- Fill in the mandatory fields, create a new Publisher or use the default value, and click on the Save icon.
Removing a solution is also a very simple process. Select the solution to be removed, and click on the Delete icon.
Tip
If this is a managed solution, all solution configurations are cleanly removed from the environment. For an unmanaged solution, the process is not as straight-forward, as the removal of an unmanaged solution will leave behind customizations and trailing components. For additional details on solution see the Solution model section of this recipe.
How it works...
Creating a new solution requires you to assign a publisher. By default, each instance of Dynamics CRM 2011 includes a default publisher for the instance. For environments where a solution is to be published to production, create a publisher that includes the organization details of the customizer.
There's more...
Solutions offer additional features such as versioning, which can be essential in tracking progress and deploying to the production environment.
Also, with solutions, we have two very important models, a managed and unmanaged solution model. A managed solution is a restrictive package, which can only be edited by specific users, and can be cleanly rolled back. An unmanaged solution on the other hand is a type of package used mostly for development environments, and it allows various developers to move customizations from one environment to another, while keeping all customizations editable by all users with the proper permissions. Unmanaged solutions, when removed, will not be removed cleanly, and will leave behind traces of customizations. For this reason, they are not the recommended way of deploying to the production environment.
See also
- For additional details on working with solutions, consult the TechNet library at http://technet.microsoft.com/en-us/library/gg334530.aspx.
- 中國國民經濟核算體系修訂問題研究
- Mastering System Center Configuration Manager
- Citrix? XenMobile? Mobile Device Management
- 項目管理（第二版）
- 國家治理能力視角的國家審計功能理論研究
- 企業能源審計與節能規劃
- 基本有用的計量經濟學
- Getting Started with Citrix VDI-in-a-Box
- 《企業內部控制基本規范》合規實務指南
- 下一場全球金融危機的到來：明斯基與金融不穩定
- 項目管理實務（第二版）
- 中國審計市場:制度變遷與競爭行為
- Building Dashboards with Microsoft Dynamics GP 2016（Second Edition）
- Getting Started with Citrix? Provisioning Services 7.0
- 審計實務