Are you using CRM 2015 and you have complaints regarding the global search 2015 performance? Well then you are right place.
with CRM 2015 Update 1, Microsoft provides a feature to enable full text search for your organization. Once you download and install Update Rollup 1 for Dynamics 2015, this option would be available to you.
Go to Settings –> System Settings.
In the Setup Quick Find Settings, you would see a new option to enable full-text search
You would need to enable it.
Don’t expect to see magic immediately. It may take up to 24 hours for full text search since maintenance job has to be run on the server and make adjustments in the specified CRM Organization. Let’s get a bit under the hood here.
When you enable full text search from your CRM, internally CRM uses the full text catalog. If you open SQL server and navigate to your CRM Organization database –> Storage –> Full text catalogs, you would find the entities mapped for full search. Please note that as I said before, this takes considerable amount of time, hence if you immediately move to your database after enabling the setting in CRM, you might not find the table mappings.
All this about technical stuff but what about end-user experience?
Well the following are the changes
- The first change that the user would notice is that they do not need to use wildcards anymore. For example – when before full text search is enable, if you search for the word test and if I take account entity, it would return all account whose any quick find column value begins with Test. However after you enable full text search, users no need to use wild card search. Search by any word and it would evaluate with contains operator.
- Full Text search enables some data science on your data. It actually returns forms of a word.
- Incorporates Pluralization (“child”, “children”, etc)
- Incorporates Tense (“drive”, “drove”, “Driven” etc)
- Now coming to performance – When I tested this in one of my customer environments, I was simply amazed and impressed by the performance. Previously when the search phrase – *Test returned results in 15 seconds. After enabling Full Text search, the query returns records in less than 2 seconds.
Before I close this out, this works only on string field. Optionset fields and likewise would not be incorporated in full-text search.
Hope this helps!