IPlugin interface and Code Activity abstract class

Why the plugins implement IPlugin interface and Workflows (custom) inherits the Code Activity abstract class

IPlugin Interface:

Have only one method i.e. Execute which we have used on our plugin code

Reference

Code Activity Abstract Class:

The structure of Code Activity abstract class, you will find it have 35 different methods

Reference

More detials

How to Find the Object Type Code for Any Entity

How to Find the Object Type Code for Any Entity

Every entity in the system will have an Object type code. For easiness of understanding, reason of it as a numbering system for all the entities, regardless if they are out of the box or custom. CRM Object Type Codes are basically split into 2 categories – system entities and custom entities. As a CRM Developer, in many cases you might encounter a situation where you will need to identify the Object Type code for an entity.

Follow the following steps, to identify the Entity name using the Object Type Code:

1.       Login in MS CRM Organization

2.       Open custom entity under any model, like Sales, Service..

3.       Open Existing Record from that entity.

4.       Once existing record is opened, pop out the record by selecting the icon on the top right side of the page.

5

.       Once enlarged, the Object Type Code is placed after the “etc.” equal sign within the URL.

Delete Components from Managed Solution in Dynamics CRM By Using Clone Solution

How to – Delete Components from Managed Solution in Dynamics CRM 2016 without using Holding Solution.

Before the updates that we have received for solution in CRM 2016 the only way to delete components from managed solution was to use Holding Solution.

The following post nicely explains this.

Now let us see how we can do this in CRM 2016 without using Holding Solution.

Suppose below is our managed solution that includes 2 Action, 2 Entity, 2 SLA, 2 Workflow.

Entity 2 with two forms.

Entity 2 with 2 Views.

 

Entity 2 with two Fields.

Now import this solution as managed in destination org.

Now suppose we do not want following components in our Destination org – action 2, dashboard 2, Report 2, Security Role 2, Workflow 2 etc. along with View 2, Field 2 and Form 2 for Entity 2.

We remove some of the components and delete (field, form etc.) from our unmanaged solution (named Core Solution) which we had imported as Managed in our Destination Org.

Deleted View 2

Deleted Field 2

Now click on “Clone to Solution“. (This will increment the version number.)

For More Info about cloning a solution following this url (https://community.dynamics.com/crm/b/magnetismsolutionscrmblog/archive/2015/12/17/dynamics-crm-2016-cloning-solutions-amp-patches)

Now import this updated solution to our destination organization, and select “Stage for Upgrade”

Click on “Apply Solution Upgrade”

This will remove the components from our destination org.