Using keyword search with wildcards

When using keyword search with wildcards in list views, the results can be confusing.
In a column search, the * symbol acts as a “contains” operator, but in a keyword search, it functions as a wildcard that broadens the search pattern.

Keyword search (without wildcards)

Keyword search does not require operators.
Operators such as * (contains), !* (does not contain), < (less than), and > (greater than) apply only to field-specific searches, not to keyword searches.

When the list header shows “Keyword” or “for text”, you are performing a keyword search.
Keyword search scans multiple fields and looks for the exact term you type.

Example:

• Searching for abcde (no wildcards) returns records containing that exact term only.

This type of search behaves similarly to an exact match and does not automatically include variations before or after the word.

---

Keyword search (with wildcards)

When you add wildcards to a keyword search, the search expands to include partial matches before or after your term, depending on where the wildcard is placed.

Using * before and after the term (for example, *abcde*) provides behavior closest to a “contains” search, since it ignores what comes before or after the keyword.

Image 1:

 

Image 2:

 

Image 3:

All Releases  

Field-based search vs. keyword search

When searching a specific field such as Number, Short description, Priority, or Caller, the platform uses field operators (for example, *, !=, <, >).

Example:
If you select Number as your filter and type *0000002, it searches for records whose Number contains 0000002.

In contrast, keyword search is not tied to a single column or field—it searches across multiple indexed fields.
When using the Condition builder (hourglass icon) and choosing “Keyword” as the condition, the only available operator is “are”, indicating that wildcards are interpreted differently than standard field operators.

• * behaves differently in keyword search than in field-specific searches.
• Keyword search without wildcards looks for exact matches.
• Keyword search with wildcards broadens results depending on placement (abcde*, *abcde*).
• Use wildcards before and after your term (*term*) for a “contains”-like behavior.

• Wildcards
• Text Searches In Record Lists.