• eLogic

Dynamics CRM Tech Tip - Modifying Quick Find Search Properties


While Microsoft Dynamics CRM features a powerful Advanced Find tool, we often find our customers using the simpler, easier to get to “Quick Find” bar located at the top right of record views.









This search function provides quick access to records and is contextual to the currently selected view.


However, out of the box, this search is limited to a small number of record properties that Microsoft has pre-defined for any given entity. While that may be a good place to start, typically you’ll want to add the fields that are most important to you as query-able, potentially even including custom fields you’ve defined within your solution.


To define which fields are searchable by the Quick Find tool, there are a couple easy steps you as an administrator can take to customize this functionality.


From your Administration Panel, select Settings > Customization.


Select Customize the System.









When the solution opens, expand Entities on the left hand navigation pane and select the entity whose Quick Search bar you would like to customize. For my example here, I’ve selected Opportunities.


Expand the entity you are modifying and select Views.




















Locate the view name that begins with “Quick Find”. In my case, that view is “Quick Find Open Opportunities.”


Select this View and double click to open the view customizer window.




















The view customizer window will appear. This is the same panel you are likely familiar with if you’ve spend any time working with the Advanced Find feature within Dynamics CRM or if you’ve built or modified your own custom views previously.


To make entity fields searchable via Quick Find, you will add the column to the view via Add Find Columns. To remove a field as searchable, simply remove the column from the same Add Find Columns list.















Save your changes, Publish Customizations and your new capabilities should be effective almost immediately!


Remember, although it may be tempting to make many entity fields searchable in this manner, that doing so will eventually negatively affect Quick Find performance, so it is best to keep the searchable fields to a minimum wherever possible.