From the Microsoft Dynamics CRM Blogs: Avoiding form reload; Routing rules; Calculated fields; Casting error

A look at the latest from the Microsoft Dynamics CRM blogs:

• Avoiding Form Reload When Switching CRM Forms Based on a Field;
• Using Routing Rule Set in Microsoft Dynamics CRM 2013;
• Calculated Fields in Dynamics CRM 2015;
• CRM 2011/CRM2013 - Investigating a Casting Error with ActivityParty

Avoiding Form Reload When Switching CRM Forms Based on a Field

This post comes to us from Gonzalo Ruiz' Dynamics CRM blog, offering a solution for avoiding a certain kind of double form load scenario.

Ruiz says quite often you define different forms for a given entity and you do a form switch based on a field rather than based on the security role of the user.

The problem with this approach is that there is often a double form load because when the wrong form loads, then the record re-loads using the appropriate form.

"The effect is bad user experience because the form loads twice so it doubles the form load time," he explains.

You can find out what the solution is here.

Using Routing Rules in Microsoft Dynamics CRM 2013

On the Himbap blog, Microsoft MVP Mahendar Pal talks about a new feature introduced in Microsoft Dynamics CRM 2013 SP1 and Microsoft Dynamics CRM Online Spring '14 that allows users define case routing rules.

Users can set up different queues based on different business scenarios and then define case routing rules to route cases to these queues, he explains.

To learn where to go to define routing rules, as well ...