CRM 2013 – MB2-703 – Customization and Configuration Certification Solution Exam Cram Notes

Here are the exam cram notes for solutions, I am assuming you have

read my blog post on solutions and you understand how solutions work and the functionality

CRM 2013 – Understanding Solutions and how they work

watched the youtube video running through adding solutions

CRM 2013 – Understanding Solutions and how they work in CRM 2013

The video going through the Solution Exam Cram notes is here

All the study notes for the MB2-703 exam can be found on the page link above or clicking the link below

https://crmbusiness.wordpress.com/mb2-703-crm-2013-customization-and-configuration-certification/

These notes are the to revise the key concepts of solutions for the MB2-703 – Microsoft Dynamics CRM 2013 Customization and Configuration certification

• Config – teams, security roles, business units, Entities, views
• Customization – standard GUI changes, forms, entities, views, GUI workflows, business rules
• Extending CRM – Code changes – javascript, .NET, plugins, custom workflow, console application
• Configuration and customization could be used when talking about changing the same components e.g. Entities, Views
• Extending = code related changes.
• Microsoft Dynamics CRM 2013 Software Development Kit is used to create and deploy plugins, Web Resources and custom workflows.

 

What cannot be added to a solution

• Business Units

• Teams

• Queues

• Goals

• Subjects

• Product Catalog

The items above must be either created manually or imported.  If you want to create manual data and use the same guids between systems then you will need to export and import the data so you can specify the guids used.

What Can be Added to a Solution?

The following is a list of solution components that you can view within a solution

1. Application Ribbon

2. Article Template

3. Business Rule

4. Chart

5. Connection Role

6. Contract Template

7. Dashboard

8. Email Template

9. Entity

10. Entity Relationship

11. Field

12. Field Security Profile

13. Form

14. Mail Merge Template

15. Message

16. Option Set

17. Plug-in Assembly

18. Process

19. Report

20. Sdk Message Processing Step

21. Security Role

22. Service Endpoint

23. Site Map

24. Web Resource

 

• Solutions in Microsoft Dynamics CRM is a method to let you group and manage your custom components for a particular set of functionality or release

• solutions are optional

• When an organisation is created a Default Solution is created which contains all the components

• You can export the default solution but only as an unmanaged solution

• Solution best practice is use it to split up business requirements probably either in Sprints/releases or in business requirements.

• It’s possible to export the Default Solution and import this solution into another CRM Instance but you cannot export Default solution from  a CRM On Premise to a CRM On line or vice versa.

• There is no limit to the number of solutions you can create

• Before you can create a solution you must create a publisher, Publisher is a business required field on solution

• A publisher has a prefix, The prefix will then be added before the schema name for the entity or field e.g.

  • hosk_newField

  • hosk_entityName

• Managed solutions cannot be exported

• unManaged solutions can be exported

• Managed solutions can be deleted, this will delete the solution and all the entities and data

• Managed solutions can’t be changed or altered, except by the publisher/owner

• There are privileges needed to import a solution and publish it.

• Managed solutions use managed properties

• Managed solutions automatically publish on import

• unmanaged solutions have to be published

• Unmanaged solution components cannot be uninstalled

• when you delete an unmanaged solution you are only deleted the solution file, all the changes remain in the default solution

• Unmanaged solutions can be exported as an unmanaged or managed solution

• Managed solutions can expose some components to be customized by the end user

• solutions have built in versioning, if version 1 is imported and then solution 2 is imported, CRM will prompt you to see if you want to overwrite the changes in version 1.

• Solution version is major.minor.build.revision

• Custom solutions developed using Microsoft Dynamics CRM 2011 can be imported into Microsoft Dynamics CRM 2013 and Microsoft Dynamics CRM Online organizations.

• Custom solutions developed using future versions of Microsoft Dynamics CRM cannot be installed into earlier versions without first being ‘down-leveled’ to match the earlier version.

• When you export a managed solution, you can’t import it back into the organization it was imported from.

• be careful when importing an unmanaged solution because those changes cannot be removed and they will overwrite any current changes

• Solutions are additive, you cannot delete any components by importing a solution

• You need the System Administrator role to import solutions

• You cannot import entities or fields with the same schema name to components that exist in the CRM database.

• All imported security roles are created in the root business unit

• managed properties are fully customizable by default.

• Solutions created in Microsoft Dynamics CRM 2013 cannot be imported into a Microsoft Dynamics CRM 2011 database.

• The maximum size for a solution file for Microsoft Dynamics CRM online is 29.296 MB

• For On-premise CRM 2013, the default maximum size for a solution is 6 MB but this can be increased.

• You must have the System Administrator security role to import , organization settings,  security roles, plug-in assemblies, sdk message processing steps.