User Review( votes)
Here are a set of 10 Tips to design CRM Views like a Pro:
- Try to limit the number of columns on the View and limit the number of scrolls that are required to be done on the View. Usually, end users do not like to scroll more than 2 times even on the Web client. Also, more the number of columns, slower the view will load as it has performance implications.
- In case views show All Records then out of box status field (Active/Inactive) makes sense to be put on the View. As an example, for “Active Accounts does not make sense to show status field since this is self-explanatory and applied at the filter level itself. The column space can be saved to add another relevant column.
- Place generic fields such as Created On/ Modified On, Created By/Modified by towards the end of your View column definition. This helps in keeping it same as out of box views shipped with the product and is useful generic information for most views
- It makes sense to give users a filtered down view for their own records. For example, for a custom entity called Procurement Request, view with filtered only for current user owned Procurement request will make sense like “My Procurement Request”
- Select the Column width appropriately depending on the need of the column from 25 px to 300 px. Remember, optimal utilization of Dynamics 365 view column space is considered a good customization practice and results in great user experience.
- Remember to set default views for users based on their need and to train them on how they can change their default view by pinning and override the ones set by System administrator.
- Ability to create Personal views need not be applicable to all the users who you use the system. Remember that this can be controlled through Security roles.
Dynamics 365 specific:
- Editable grids should be only put for relevant Entities, Views, etc.
- Try to utilize the new editor available for the Unified interface which is part of App Designer. One of the key features of this editor is the ability to preview records in the designer itself which distinguishes it from current View editor available in web client.
3. For Apps select only the relevant views for the Apps using App designer. It does not make sense to include all the views in the Apps for a given entity. Instead, only include the ones which are more relevant for the App based on usage.
Hope it helps and happy 365ing!
Any problem in CRM – end user,Microsoft partner or an individual?
Problem Area – Technical, Functional, Training, Development or consulting?
I am here to help, get in touch here: Click here
ABOUT THE AUTHOR:
Google Play Store: