Overview
There are some differences that are not described in other documentation and might cause confusion. This article describes those special cases.
No wildcards
Smart Search does not use any wildcards in searches. Still, you might get confused when searching a document including word agreement with a search phrase agreeme* and you find it. This leads us to the next specialty.
Typo correction
There is an intelligence in Smart Search that allows typos (spelling mistake) in searches. To be able to work properly, it will need certain length for the word for certain correction capability. Current lengths are 4 for one typo and 8 for two typos.
For example, if you try to find a document with a word link and you mistakenly use a search phrase lonk, the search will find the object. Instead, if you try to find bug with nug, the search does not find the object.
The above will explain, why the wildcards often seem to work, although they are just part of the typo correction.
No Number (integer) Data type in quick search
We do not support the quick search of Number (integer) Data types. To work around this, either use MetaData field search or create a separate Property with Text data type and copy the integer Property values into it.
Restricted MetaData field search
MetaData field searches are limited in Smart Search. Only numerical and lookup typed fields can be searched and only with IS operator.
