“Customer” type field in Dynamics CRM

Posted on

Microsoft has finally introduced the Customer type field in Dynamics CRM. This was a much awaited feature which now allows developers to create a Customer field and not separate lookups on Contact and Account

CustomerType

Dynamics CRM Demo Builder

Posted on

Have you tried the new Dynamics CRM Demo Builder – https://www.microsoftdynamicsdemos.com

It is really awesome and it takes only a couple of minutes to provision an industry specific vertical demo of Dynamics CRM.

The only catch is that this is accessible only if you have a Microsoft Partner account.

Solution Strategy and Solution Management in Dynamics CRM 2016

Posted on

Microsoft has recently released Dynamics CRM 2016 that has whole bunch of new and exciting features. One of the features that will help the Developers is around Solution Management.

In previous versions of Dynamics CRM, adding an entity to a Solution would add all the components. But, in Dynamics CRM 2016, Developers would be able to select the specific components while adding it to a Solution –

 

CRM 2016 - Solution

This features ensures that only required components are added and the size of the solution is minimal.

 

How to check if two records are related N:N

Posted on

QueryExpression query = new QueryExpression(relationshipName)
     {
         NoLock = true,
         ColumnSet = new ColumnSet(false),
         Criteria =
         {
             Filters =
             {
                 new FilterExpression
                 {
                     FilterOperator = LogicalOperator.And,
                     Conditions =
                     {
                         new ConditionExpression("accountid", ConditionOperator.Equal, accountID.ToString()),
                         new ConditionExpression("contactid", ConditionOperator.Equal, contactId.ToString()),
                     },
                 },
             }
         }
     };
     var result = service.RetrieveMultiple(query);
There is a catch here, if you have created a self referential N:N relationship then the primary fields are “<fieldname>one” and “<fieldname>two”, so incidentidone and incidentidtwo