Relationship Behavior in MS CRM

The relationship behavior feature of CRM handles action output as per specified settings. Like you can decide major actions Assign, Delete, Share to be handled properly. Say you assigned accounts from one user to another user and in this action you also need to assign all active calls to new user but not need to assign completed call then in such scenario you need to provide relationship behavior of Account-Phone Call entity to Configurable Cascading and set apply rule as “Cascade Active” for Assign action. This will apply changes as per discussed above.

The different type of behaviors provided are,
Parental
 In a parental relationship between two entities, any action taken on a record of the parent entity is also taken on any child entity records that are related to the parent entity record. if you delete a record in the parent entity, the related child entity records are also deleted; or if you share a parent entity record, the related records from the child entity are also shared. All option are disable for Parental relationship
Referential
 In a referential relationship between two entities, you can navigate to any related records, but actions taken on one will not affect the other
Referential, Restrict Delete
 Actions taken on parent will not affect child record but parent record cannot be deleted till the child record exists. i.e you cannot delete a record when related records exist.
Configurable Cascading
 You need to specify your setting here.

The type we are interested here is “Configurable Cascading”. It allows you to decide what type of behavior we need to apply.

The useful details of different cascading rules are (note here me is referred to the user on whom you will perform actions)
1.  Cascade All: Perform action on all of my child records. Like if assigned my account to another user then all my activities, orders, invoices etc are assign to new user including open, completed and other user owned records
2. Cascade Active: Perform action on only my active child records
3. Cascade User-Owned: Perform action on all my child records which is owned by me
4.  Cascade None: do nothing to my child records
5. Remove Link: remove link from child record
6. Restrict: Applies to Delete. The delete is not allowed if there are other entity instances that reference the ID of the entity instance being deleted.

Hierarchy Visualization in MS CRM

Another new feature added in Microsoft Dynamics CRM 2015 is hierarchy visualization of your data. In Microsoft Dynamics CRM, we can associate entities using entity relationships. Hierarchical visualization provides logical visualization of the 1:N relationship or self-relationship between entities. At present, we can have only one hierarchical relationship per entity. While setting up a relationship, we can select whether we want to use this relationship as hierarchical using the

Hierarchical dropdown.

Once the relationship is set up, we can navigate to Hierarchy Settings --> New under the entity node to create the hierarchy setting. As soon as the hierarchy setting is created per entity, the new button will not be available anymore because we can set up only one hierarchy setting per entity:

Once the hierarchy setting is set up and the record is associated, we can see a logical relationship visualization using the hierarchy icon on the entity grid view or entity form. The following screen represents the hierarchy visualization for the parent account. We can see that Adventure Works (Sample) is a parent account and it has two child accounts. Data is represented in tiles, where a maximum of four fields are allowed. The data fields are represented from a default quick view form. If it has more than four fields, then only the first four fields are used for display:

Two new query operators are also added for querying hierarchical data, which are explained as follows:

• Under: This is used to get the list of entities, which are child entities of a

specific entity, for example, list out all subaccounts under a particular account

• Note Under: This is used for reverse of the under operator.

What is Business process flow in Microsoft Dynamics CRM

Microsoft has introduced a new feature in MS CRM 2015 i.e Business Process flow which is very useful when the requirement is based on any process flow, I am trying to what exactly business process flow and how it works in MS CRM-

Every business has some predefined business process workflows that they follow
in day-to-day business. Let's take a very common scenario of the loan approval process.
Let's assume you are a technical consultant in finance based company and wanted to implement Loan Origination system in MS CRM.

When customer apply for loan. As soon as customer apply for loan, it will
initiate a loan origination process approval behind the scenes, which may contain different stages and
sub approval of your different business owners and respective departments. Like in first stage the loan application goes to get verified with the customer address details and banking history, then it will go though the documents verification process, after document verification process is completed application will go to credit manager for the approval, in some cases this approval can be a two stage., then it will go for singing the agreement and finally the loan application will go to the disbursement team.

We can implement similar business requirements in Microsoft Dynamics CRM 2015
using the business process flow. The business process flow was introduced in CRM
2011 Polaris release initially and enhanced in Microsoft Dynamics CRM 2015. Business
process flow is basically a guided approach to complete any business process, which
may have different stages based on business requirements. Microsoft Dynamics CRM
2015 provides a rich editor to design for designing business process flow.

You can create a business process flow by navigating to Settings --> Process --> New and selecting
Business Process Flow under the Category drop-down menu.

We can have up to 30 stages and 30 steps per business process flow.

We can include multiple entities in the same business process flow and take the process flow from one entity to another entity. We can include up to five maximum entities in the business process flow. The following is the screenshot of the out-of-the-box Lead to Opportunity Sales Process business process flow:

Microsoft Dynamics CRM 2015 added support for branching logic, which allows us to switching the process stage using if conditions, the logical AND and OR operator support, which allows us to group multiple conditions and support for interacting with the business process flow using client-side scripting for developers.