Text Search¶
In this article:
See also:
List view text search¶
On the record list view, it's possible to perform text search.
The field list which is used in filtering can be configured under: Administration > Entity Manager > {Entity Type} > Edit > Text Filter Fields.
It's possible to use a wildcard *.
There is an option to force the system to use the 'contains' operator for Varchar fields by default. Parameter is available under Administration > Settings. Note that it can affect performance.
To disable previous search suggestions, uncheck the checkbox at Preferences > Misc > Disable text filter storing.
Global search¶
The Global Search performs search in multiple entity types simultaneously.
The list of entity types used in the Global Search can be configured under Administration > Settings > Global Search Entity List.
The field list which is used in filtering can be configured under Administration > Entity Manager > {Entity Type > Edit > Text Filter Fields.
Full-text search¶
Full-text search provides the ability to perform much faster and comprehensive text search.
The Full-text search can be enabled for a specific entity type under Administration > Entity Manager > {Entity Type} > Edit > Full-text search.
After enabling of Full-text-search, running rebuild is required. If you have many records, it's recommended to run rebuild from CLI: php rebuild.php.
The Full-text search is always applied in the Global Search for entity types with enabled full-text search.
The Full-text search is also applied when you search in the list view. Though it can be skipped for some search queries. Yet, it's possible to force a full-text usage by prepending ft: to your search query.
The following operators are available:
+– A leading plus sign indicates that this word must be present.-– A leading minus sign indicates that this word must not be present.- no operator – The word is optional, but the rows that contain it are rated higher.
*– The truncation (or wildcard) operator. Appended to the word to be affected."– A phrase enclosed within double quotes must be contained literally, as it was typed.
Minimum word length¶
The MySQL option ft_min_word_len defines a minimum word length available for full-text search. By default, it's set to 4. You might want to set it to 3 to be able to search shorter words.
If you change this parameter in MySQL, you also need to run rebuild in Espo.
Stopwords¶
MySQL has the list of stopwords that are ignored by full-text search. E.g. hello.
Autocomplete¶
When Full-text search is enabled, autocomplete in link fields may not show suggestions until you type a full word. To have suggestions work for word parts, you can enable the parameter that will append the wildcard operator automatically for autocompletion queries. Administration > Settings > Append wildcard in quick search.