Limitations for Non-English Terms

Natural language search offers full support for English language queries. It can also understand queries using non-English languages, but there are some limitations. If a non-English query isn’t supported, Einstein Search does a keyword search instead.

Non-English Queries That Einstein Understands

You can enter non-English language queries with this text:

Note If your query includes non-English search terms that Einstein Search can’t interpret, it defaults to a keyword search.

Supported	Example
Renamed Supported Objects (Account, Case, Contact, Knowledge, Lead, and Opportunity)	Einstein Search treats object names as they're written, regardless of the language. If you rename any objects to your local language, you can use the renamed value in a search. Example: If you rename opportunities (English) to oportunidades (Portuguese), you can search for my oportunidades.
Renamed Fields	Similar to English, if you rename a field, you can only search using the new name. Example: A French user renames the field stage to étape and opportunities to opportunités, but the value for this field, qualification, remains in English. So, to search for opportunités étape qualification is a valid search, but opportunitiés stage qualification isn’t. If you enter an invalid query, the search defaults to a keyword search.
Picklist Field Values	Searches that include a value for the supported picklist fields are treated as literal text, regardless of language. Example: You change the value of the opportunity field stage from new to nouveau. The search for opportunity stage nouveau returns results, but opportunity stage new doesn’t.

Supported

Example

Renamed Supported Objects (Account, Case, Contact, Knowledge, Lead, and Opportunity)

Einstein Search treats object names as they're written, regardless of the language. If you rename any objects to your local language, you can use the renamed value in a search.

Example: If you rename opportunities (English) to oportunidades (Portuguese), you can search for my oportunidades.

Renamed Fields

Similar to English, if you rename a field, you can only search using the new name.

Example: A French user renames the field stage to étape and opportunities to opportunités, but the value for this field, qualification, remains in English. So, to search for opportunités étape qualification is a valid search, but opportunitiés stage qualification isn’t. If you enter an invalid query, the search defaults to a keyword search.

Picklist Field Values

Searches that include a value for the supported picklist fields are treated as literal text, regardless of language.

Example: You change the value of the opportunity field stage from new to nouveau. The search for opportunity stage nouveau returns results, but opportunity stage new doesn’t.

Natural Language Searches That Work Only in English

Some expressions and values can be interpreted only in English.

Supported	Example
Boolean Field Values	For a boolean field, that is, a field where the only options are true or false, natural language search only supports English-defined values. Example: For cases, the Escalated field, a boolean field, is renamed to Escalado (Portuguese). But if you search for escalado casos, the query doesn’t work and it defaults to a keyword search.
Date	Date fields only work with English date expressions, not local time expressions, so casos last month works because the last month is in English. But the query casi il mese scorso (Italian) doesn’t work. Only SOQL dates or date literals are supported. A date literal is a fixed expression that represents a relative amount of time, such as last month, this week, or next year. For more information, see Date Formats and Date Literals in the SOQL and SOSL Reference guide.
Operators	Search doesn’t translate the operators "top" and "my", but you can combine these operators with non-English words. Example: The query my casos (Spanish) is a valid query, but mis casos isn’t.
Stopwords	Natural language search ignores English stopwords, which are common words that can be safely ignored because they don’t add to the meaning of a sentence. Searches that contain non-English stopwords don’t work, so search defaults to a keyword search.