Skip to main content

Notifications

Announcements

Share Your Journey with Power Pages and Help Shape Its Future!
News and Announcements icon
Dynamics 365 Community / Blogs / Dynamics 365 Blog by Guowei Xu / Best Practices for Dynamics...

Best Practices for Dynamics 365 CRM Quick Find View

Guowei_Xu Profile Picture Guowei_Xu 407

Overview

There are many types of System Views,  the following table lists all.

System Views Description
Quick Find   The default view used when searches are performed using Quick Find. This view also defines which columns are searched when using search capabilities of Quick Find and Lookup views.
Advanced Find The default view used to display results when using Advanced Find. This view also defines the columns used by default when new custom public views or personal views are created without defining a view to use as a template.
Associated The default view that lists the related tables for a record.
Lookup The view that is displayed when you select a record to set for a lookup column.

Today, I'd like to share some best practices regarding the Quick Find view.

Quick Find View demo in Dynamics 365 CRM

For example, you can search Accounts by inputting keywords in the top right text box. The accordingly result view is the Quick Find View.

pastedimage1682493417391v2.png

You can customize the Quick Find view in the backend solution designer.

pastedimage1682494164819v3.png

pastedimage1682494220629v4.png

Best Practices for Quick Find View

When using the quick find feature for a table, the results are displayed in the table’s Quick Find view. When customizing this view, you can define the columns returned, sorting and filter criteria, and the columns (fields) that will be searched.  
A few best practices to keep in mind with Find Columns:

  • Limit the number of fields to be searched to ONLY those that need to be searched.
    • If possible, try to keep this under 10 fields
  • Avoid selecting fields with the following data types:
    • Multiple Lines of Text
      • This includes the composite address fields
    • Option Set
    • MultiSelect Option Set
    • Status Reason (statuscode)
    • Two Options
    • Calculated Fields
      • The fields with the above data types are NOT able to be indexed.  Having just one field with any of these data types will result in a slow search if the entity has many records.
  • Leading wild card searches
    • Users that use a leading wildcard for quick find searches should expect to see slower performance on entities with large amounts of data. In these scenarios, the platform will not be able to utilize the indexing that is in place.

Quick Find Record Limit

The Quick Find record limits setting will limit the results of quick find.  If more than 10,000 records are found, a message will be displayed to the user that suggests a more selective search.

This setting default value is set to Yes, which is the recommended setting.

You can find this setting through PPAC. Environment->Settings->Features

pastedimage1682493055347v1.png

If this setting is set to No, the platform cannot utilize the quick indexes, which may result in low performance.

More

This is a series of blogs introducing the Development Standards and Best Practices to help configure and customize CRM to do so consistently, clearly, and meaningfully.

Please refer to this page for all the content. 

Dynamics 365 CRM Development Standards and Best Practices.

Comments

*This post is locked for comments