Difference between Share Vs Assign in MSCRM

SHARE	ASSIGN
User who has share privileges on entity record can share to another user	User who has Assign privileges on entity record can share to another user
On sharing the record, selected permission given to new user on that record.Here, ownership of the record remain same.	On Assigning record, Ownership will be transferred to new user
We can use Grant Access, Modify Access and Revoke Access Messages to share the records with SDK	We can use Assign Request to assigned records with SDK

Difference between Append Vs Append To in MSCRM

 ‘Append’ and ‘Append To’ privileges works together in CRM. ‘Append To’ allows other entities to get attached with it. ‘Append’ privilege will allow the entity to attach the records of an entity which has ‘Append To’ privilege.

Ex:
Generally, we attach notes to an entity (Account). To do this Note should have “Append” privilege and Accounts should have “Append To” privileges.

Difference between Global Option set AND Normal Option set field in CRM

 In Dynamics 365, there are 2 types of option set fields, global and local. Global option sets are stored at a “global” level and can be used in any entity. This is different from local option sets, which are available only to the entity they are created in. Having an option set at a form level is beneficial if, say, you have unique attributes for the field and therefore having it globally wouldn’t make sense. If you reuse the field in many entities, having a global option set would make sense.

Difference between Workflow AND Dialogue

Workflow :- Are asynchronous processes, and do not allow/require user input to run to completion. These processes run in the background. Dialogue :- Are synchronous processes and require user input to run to completion. When you run these processes, a wizard-like interface is presented to you so you can make appropriate selections to run the processes.

Difference between Plug-in AND Workflow in MSCRM?

• When we are using Plugin, we have a number of triggers available (called as Steps/Message) to trigger the plugin execution, • Where Custom workflows are triggered by standard workflows available in CRM, that make the custom workflow triggers limited(Create, Update, Status Change, Delete and on assign). • Workflows and by extension, custom workflow activities, execute totally asynchronously. Plugins can execute both asynchronously and synchronously. • Plugin overall execution time is lesser then workflows and if validations are required to be performed then plugins should be preferred. • Workflows can be manually executed, or automatically triggered by selected events. Workflows can be limited to automatically execute within specific organizational scopes (i.e. Org, BU, Parent and Child BUs, or for the Owner only). Plugins are always triggered by the messages to which they’re subscribed, though some Messages allow limiting execution based on whether certain attributes have been passed into the Message. • Workflows can be turned off (by unpublishing). Plugins are always on. Custom workflow activities can be used in many Workflows. Workflows can be developed through the Workflow design interface. Plugins must be developed in Visual Studio. Workflows do not require compiling (though custom workflow activities do). Plugins and custom workflow activities must be compiled and deployed through processes external to CRM.

Difference between Managed Solution AND Unmanaged Solution

Unmanaged Solution : All solutions starts out as Unmanaged. When it is in the Unmanaged state, you can add, remove, update, and test any of the components of the solutions. You can delete components of your unmanaged solutions, while leaving it available for use in the rest of the system some on the MS CRM dev team have linked this to your ‘Source’ code of your system. The great thing about an unmanaged solution is that during developments, you can create restrictions (like ‘not customizable’) on the components as they evolve. Managed Solutions : When your unmanaged solution is ready for the show, you simply export it too ‘Managed’. You could think of this as ‘compiling’ you code. You set the restrictions (i.e., prevent customizations on certain components) and the end user lives by those rules. But remember, they can still customize the components of the solution that are unrestricted. You cannot add or remove components of a solution, even if the component is unmanaged. Once you have packaged the Managed Solution, it can be installed into another organization. They can also be deployed across multiple deployment types (Online, Partner Hosted, On-Premises) and all CRM Clients (web, Outlook, Mobile Express, and Offline via Outlook Client).

Difference between Discovery service AND Organization service

Discovery Service : The Discovery service web service is used to determines the organizations that a user is a member of, and the endpoint address URL to access the OrganisationService Web service for each of those organizations this discovery service is necessary because Microsoft Dynamics CRM is a multi-tenant environment a single Microsoft Dynamics CRM can host multiple business organizations. By using the discovery web service, your application can determine the endpoint address URL to access the target organisation’s business data. Organization Service : It is a primary web service that accesses data and metadata of an organization. This web service contains the methods that you use to write code that uses all the data and metadata in Microsoft Dynamics CRM.

What is meant by publisher and why we are using it in CRM 2016?

Every solution in a CRM has a Publisher. Publisher record stores the information like address and contact information of solution publisher. CRM default solution has its default publisher with the name “Default Publisher For” We can create our own Publisher for solution and can define the “Prefix” for the custom components and start value of Option set values.

What is meant by Managed Properties?

We can’t customize managed solution components. By using managed properties of managed solution user can customized these managed solutions

What is meant by web resources and how many types of web resources we have?

Web resource is one of the components in CRM to create JS, HTML, Silverlight, Image, and style sheet files. We can create below types of web resource in CRM: • WebPage (HTML) • Style Sheet (CSS) • Script (Jscript) • Data (XML) • Image (JPG) • Image (PNG) • Image (GIF) • Silverlight (XAP) • Stylesheet (XSL) • Image (ICO)

What are components we can add from solutions?

• Application Ribbon • Article templates • Business rule • Chart • Connection Role • Contract Template • Entity • Entity Relationship • Field • Field Security Profile • Form • Mail Merge Template • Message • Option set • Plug-in Assembly • Process • Report • SDK Message Processing Step • Security Role • Service End point • Web Resource

How can we know the Owner of Managed solution?

Each managed solution is linked with Publisher. Publisher indicates the owner of the managed solution who developed it

What is the process to update Managed solution?

By using managed properties of managed solution

Can we update the components in Managed solution?

No, we can’t Update the component in managed solution

What is Unmanaged Solution?

Unmanaged Solution is a group of unmanaged customizations. Any unmanaged customized solution component can be associated with any number of unmanaged solutions. we can export an Unmanaged solution as Managed solution. We can’t rollback the customization once import into CRM instance

What is Managed Solution?

Managed solution is a kind of completed package that we can distributes to others to install in their CRM Organization

Can we export Default solution as “Managed Solution”?

No, We can’t

What are types of solutions in MSCRM?

There are two types of solutions • Managed Solution • Unmanaged Solutio

What is the importance of “Manager Properties” on CRM components?

We can’t customize component of managed solution by the using of manage properties we can customize the components of managed solution

What are the settings we need to do to see the entity relations from Advanced find?

First, make the relationship visible by customizing the relationship and setting it to “Use Plural Name”. Then save and publish your customizations. However, when setting the relationship to visible it will automatically be put into the Course Form left hand navigation pane. Then, go into the course form and remove the course category item from the navigation pane. And remember to Publish your Customization The end result look the same, but relationship is searchable.