Microsoft Dynamics CRM Solutions - Microsoft Dynamics CRM

What is Microsoft Dynamics CRM Solutions?

Solutions provide a framework for packaging, installing, and uninstalling additives to match your business functionalities. solutions permit the customizers and developers to writer, package, and preserve units of software that extend CRM. Any customizations, extensions, or configurations completed in CRM are packaged, controlled, and allotted using solutions. The solutions can be exported as a zip file from the source organization, that can then be imported in the target company.

For information this, remember the following example scenarios −

  • You, as a developer or customizer, have extended or customized CRM within the development surroundings. Now you need to package your modifications and flow it to the following environment. For this, you may create individual solutions and publish them in higher environments.
  • You, as a third party CRM company, have created a CRM module, which allows managing information in Microsoft Dynamics CRM entities using outside web provider APIs. Now, you want to promote this module to other clients. the use of solutions, you may package this module and distribute them to different customers who may be able to install this solution and use the functionalities provided through your module.

Types of Solutions

Default System Solution

The device solution includes the out-of-the-box solution components described within Microsoft Dynamics CRM without any customizations. many of the components in the system solution are customizable and can be used in controlled solutions or unmanaged customizations.

Throughout this tutorial, we did not create any answer and have been customizing the default device answer. if you consider, we went to Settings → Customizations → customize the system. this selection directly customizes the default solution.

Managed Solution

A managed solution is a solution this is finished and supposed to be allotted and installed. controlled answers can be installed at the top of the system solution or different controlled solutions.

Important Points −

  • If you export a controlled answer from one organization and import it to another, you may’t edit the answer in the new organisation.
  • A controlled answer does not immediately reference the system solution.
  • Uninstalling a controlled solution uninstalls all of the customizations related to the solution.
  • By default, a controlled solution can’t be customized in the target organization. but, using the concept of controlled properties you may outline whether a solution component may be customizable and if yes, then which specific parts of the factor may be customizable once the solution gets exported as a controlled answer.

Unmanaged Solution

An unmanaged answer is a solution that is still below improvement and not intended to be allotted. an unmanaged solution includes all of the unmanaged customizations of CRM components including any introduced, modified, removed, or deleted additives. through default, any new answer is an unmanaged solution. but, you may export an unmonitored solution as a controlled or unmanaged solution.

Important Points −

  • If you export an unmanaged answer from one organization and import it to another, you may edit the solution in the new organization.
  • An unmanaged answer at once references the system solution. for this reason, the changes made to one unmanaged answer can be applied to all of the unmanaged solutions that references the same components, which includes the system solution.
  • If you delete a solution aspect from an unmanaged answer, the component receives deleted completely from the gadget and will now not be to be had. if you just need to remove the component from precise unmanaged solution, use remove instead of delete.
  • Uninstalling an unmanaged solution does not remove the related customizations. It just deletes the solution from the system, but the changes you made will still be there.

Solution Components

A solution may be used to package the subsequent components which can be customized using default, unmanaged, or controlled solutions.

Component Type

Component

Schema

Entities

Attributes

Relationships

Global Option Sets

User Interface

Application Ribbon

SiteMap

Forms

Entity Ribbons

Web Resources

Analytics

Dashboards

Reports

Visualizations

Process/Code

Processes

Dialogs

Workflows

Plugins

Assemblies

Processing Steps

Templates

Mail-merge

Email

Contract

Article

Security

Security Roles

Field Level Security Profiles

Creating a Solution

Step 1 − Navigate to Settings → Solutions. Click New.

Microsoft Dynamics CRM - Solutions

Step 2 − in the window that follows, input the following information and click save and close.

Display Name − sample answer (this can be any call that you want).

Name − will be automatically set based at the display call. but, you may exchange this.

Publisher − Default writer. solution writer presents a common customization prefix and option value prefix. Defining a solution publisher controls how your controlled answers can be updated once distributed. however, for this example and for maximum of the general cases, you may set this as Default publisher.

Version − Specify a version with the following format: important.minor.build.revision. for example: 1.0.0.0.

Microsoft Dynamics CRM - Solutions

By default, each solution is introduced as an unmanaged answer. once a solution is introduced, you may upload answer components through developing them in the context of this answer or through including the existing components from different answers. for example, you may create new entities, forms, etc. in the context of this new solution.

Exporting A Solution

Once you have all of the changes in place that you want to package as a controlled or unmanaged answer, you may export your answer as follows.

Step 1 − Open the source organization and navigate to Settings → solutions. choose the solution that you need to export and click the Export button.

Microsoft Dynamics CRM - Solutions

Step 2 − In the Publish Customizations window, click Publish All Customizations and then click Next.

Microsoft Dynamics CRM - Solutions

Step 3 − in the window that follows, you may optionally choose any device setting including auto-numbering, calendar settings, etc. to be exported with the answer. For now, you may avoid selecting any choice and click next.

Microsoft Dynamics CRM - Solutions

Step 4 − in the package type window, you may choose whether you need to export the package as a controlled or unmanaged solution. For this example, let us export it as unmanaged. once achieved, click next.

Microsoft Dynamics CRM - Solutions

Step 5 − In the next window, you can see the source version of CRM that you are using and can select the target version. Click Export.

Microsoft Dynamics CRM - Solutions

Step 6 − Once you click Export, the solution will be exported as a zip file. Save this zip file at a desired location on your system.

Microsoft Dynamics CRM - Solutions

Importing A Solution

Now, we can import the answer zip file that we exported inside the previous section to a new target organization.

Step 1 − Open the target organisation and navigate to Settings → solutions. click Import.

Microsoft Dynamics CRM - Solutions

Step 2 − Browse the zip file that you downloaded from the export step and click Next.

Microsoft Dynamics CRM - Solutions

Step 3 − From the following window, you may view the answer package information if needed. Clicking Import will start the solution import process.

Microsoft Dynamics CRM - Solutions

Step 4 − once the import method completes, it will display the status of success or failure. If the method succeeds, click on submit All Customizations. In case the solution importing fails, it will give you a detailed mistakes log on which step of the import technique failed.

Microsoft Dynamics CRM - Solutions

Step 5 − We’re performed. the solution may be successfully imported to the target organization. click near.

Conflict Resolution

Since you may have multiple developers running on customizing and increasing CRM, you may have multiple controlled and unmanaged answers. Exporting and importing these answers can sometimes result in conflict scenarios. for example, suppose ‘answer A’ includes a field on a shape while ‘answer B’ has removed the field and ‘answer C’ has renamed the field. in this situation, what will be the final change? In such conflicting scenarios, CRM uses approaches.

Merge − This technique is used for user interface components including command bar, ribbons and site maps. As according to this technique, the solution components are re-calculated from the bottom and the organization’s unmanaged customizations are the last to apply.

Top Wins − This technique is used for all different conflict scenarios except the person interface components. As per this technique, the last alternate (either managed or unmanaged) takes the priority and gets applied.

Conclusion

In this chapter, we added the concept of answers and unique types of answer and their components. We then learnt how to create, export, and import an answer. Finally, we studied about the two conflict resolution techniques, which takes place when we have multiple controlled and unmanaged answer affecting the same answer components.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Microsoft Dynamics CRM Topics