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.