Best Practices: Managing Forms in Microsoft Dynamics CRM
Posted by Lauren Christoff on June 27, 2016
Following best practices when designing and customizing forms in Dynamics CRM will help you to get optimal speed and performance out of your system.
Here’s a recap of some of the rules we try to follow when designing Dynamics CRM forms for clients.
- Form load time will increase as you add items to the form and it causes visual clutter - less is best.
- It’s recommended to remove and delete fields, sections, and tabs that you are not using.
- If you are using tabs, place the most important attributes in the first tab on the form, and collapse tabs when possible
- Collapsed tabs do not load until they are expanded
- Limit triggers and plug-ins to as few entities as possible and querying as few entities as possible.
- Do not associate the plug-ins on a retrieve or RetrieveMultiple request that happens every time a user views data in the system.
- With data requests, less data and fewer requests is more.
- In Jscript, sub-grids, and plug-ins, retrieve only the data that is needed as the time, rather than getting everything and filtering through a general result afterwards in the code. This will reduce time to return the information, as well as the processing time it takes to sort through it. Before writing a retrieve, determine which columns from an entity are needed first.
- Sub-grids, charts, and iFrames should be used only when needed. Multiple sub-grids on a form can greatly impact the performance of a form because they are data intensive. If you have the requirement to add multiple sub-grids to a form put them in tabs that are collapsed by default so the data is only loaded if the user expands the tab.
Crestwood has expert Dynamics CRM consultants at your service!
Need some help with forms? Email us at Support@Crestwood.com