Configure Quick Find options for the organization

Dynamics CRM 2015

Applies To: Dynamics CRM 2015

The Quick Find search feature provides quick results to users who input simple queries to commonly searched entities. You can tailor the Quick Find functionality by selecting record return limits, indexing method, and which entities are included.

By default, Microsoft Dynamics CRM uses the same search functionality as was available in previous releases, which is based mostly on string matches.

System administrators have the option to use full-text indexing for Quick Find. We recommend that you enable full-text indexing for Quick Find because it can provide a better search experience by improving query performance. Full-text search also uses more sophisticated indexing methods that includes support for linguistic-based searches and superior relevance ranking.

While the previous search method (standard indexing) returns results based on literal matches, full-text indexing returns linguistic-based matches. For example the term service can return similar words like servicing and serviced. More information: Full-Text Search (SQL Server)

To find information, standard indexing often requires users to add wildcards to search strings. This results in poor performance for large datasets, due to the required full table scans instead of using an index. Full-text indexing doesn’t use wildcards, which leads to improved query and system performance. Notice that, although users can include wildcards in search strings, wildcards are ignored.


Microsoft Dynamics CRM 2015 Update 0.1 (on-premises) or a later version is required to use the full-text indexing for Quick Find feature. Notice that this feature is currently not available with Microsoft Dynamics CRM Online. More information: Microsoft Dynamics CRM 2015 Update 0.1

Changes made to how and when Microsoft Dynamics CRM data is indexed are not initiated until a certain time of day, typically during the late evening. Before you enable or disable full-text indexing, consider the following.

  • Because indexing is a maintenance job that runs one-time every day, it can take up to 24 hours for the system to enable or disable full-text search, or add and remove find columns.

  • When customizers add an item for Quick Find, such as adding a find column, the column data won’t appear in Quick Find search results until the next maintenance job completes. These items can still be discoverable through Quick Find searches, but will use the previous search method. Any columns that have not finished indexing for full-text will continue to use the standard indexing method for Quick Find searches. When indexing for a column completes, Quick Find will use full-text search. Notice that, when full-text search for Quick Find is enabled, columns newly added to a Quick Find view will not have any indexing until the next maintenance job completes. This may cause poor Quick Find performance.

  • Advanced Find search is not affected when you enable full-text indexing for Quick Find. Advanced Find will continue to use the same standard indexing that was available in previous releases of Microsoft Dynamics CRM.

  • Because full-text indexing for Quick Find uses SQL Server full-text indexing, certain queries made up of mostly or entirely common words (stopwords such as on, or, for, and, like) may not return expected results. SQL Server database administrators can create a custom stoplist or choose not to use a stoplist by dropping the system stoplist (not recommended). More information: TechNet: Configure and Manage Stopwords and Stoplists for Full-Text Search

This section is specific to Microsoft Dynamics CRM (on-premises) deployments.

When you enable full-text indexing for a database with a large number of columns, the size of the transaction log of the organization database may increase. We recommend that you monitor and consider shrinking the transaction log. More information: MSDN: Manage the Size of the Transaction Log File

The aspects of resource consumption for full-text indexing are different from standard indexing, which may lead to SQL Server performance issues. Performance can especially be affected during the initial full-text indexing for all Quick Find text fields. More information: MSDN: Improve the Performance of Full-Text Indexes > Common Causes of Performance Issues

Index creation is a background process so for large amounts of data serviced by busy SQL Servers, it can take several hours to multiple days for the full-text indexes to fully complete.

Before you enable or disable full-text indexing for Quick Find, review the preceding What system administrators should consider before enabling or disabling full-text indexing section.

  1. Settings > Administration > System Settings >General tab

  2. Select Yes of No next to Enable full-text search for Quick Find.

© 2016 Microsoft Corporation. All rights reserved. Copyright