- 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.
- Pentaho Business Analytics Cookbook
- 審計學
- Splunk：Enterprise Operational Intelligence Delivered
- EViews10.0的應用與計量分析
- Learning Microsoft Azure
- 風險導向審計準則實施效果研究
- 高級計量經濟分析及Stata應用
- 2017年度注冊會計師全國統一考試專用教材（圖解版）：審計
- Business Intelligence Cookbook：A Project Lifecycle Approach Using Oracle Technology
- Stata統計分析與行業應用案例詳解（第2版）
- 內審人員進階之道：內部審計操作實務與案例解析
- Oracle E-Business Suite Financials R12：A Functionality Guide
- INSTANT IBM Lotus Notes 8.5.3 How-to
- Managing Virtual Infrastructure with Veeam? ONE?
- 效益實現管理實踐指南