---
schema_version: "1"
id: 54d47f0326a9818a91508bce5abfc851e116372448df8ecc011dc8e6c13d8ddf
title: Limitations for Non-English Terms
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ai/264-0-0/search_ai_nonenglish_nls.md
canonical_url: https://help.salesforce.com/s/articleView?id=ai.search_ai_nonenglish_nls.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 74563d88dfd05f2f470f53c9ed3ed9d17634b57b92c113dcc3e3cd20f0f3e462
description: 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.
products:
  - Cross Cloud
release: "264"
---
# 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ai-search-264-0-0-production-enus/6a28c936-3b68-4186-bc09-7ab905f33ef3/images/icon_note.png)

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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d41398e47">Supported</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d41398e50">Example</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Supported" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e47 ">
              <p style="margin-bottom:0;">Renamed Supported Objects (Account, Case, Contact, Knowledge, Lead, and
                Opportunity)</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e50 ">
              <p>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.</p>
              <p style="margin-bottom:0;">Example: If you rename opportunities (English) to oportunidades (Portuguese), you
                can search for my oportunidades.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Supported" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e47 ">
              <p style="margin-bottom:0;">Renamed Fields</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e50 ">
              <p>Similar to English, if you rename a field, you can only search using the new
                name.</p>
              <p style="margin-bottom:0;">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.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Supported" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e47 ">
              <p style="margin-bottom:0;">Picklist Field Values</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e50 ">
              <p>Searches that include a value for the supported picklist fields are treated as
                literal text, regardless of language.</p>
              <p style="margin-bottom:0;">Example: You change the value of the opportunity field
                <strong class="uicontrol">stage</strong> from new to nouveau. The search for opportunity
                stage nouveau returns results, but opportunity stage new doesn’t.
              </p>
            </td>

          </tr>
        </tbody>
      </table>

## Natural Language Searches That Work Only in English

Some expressions and values can be interpreted only in English.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d41398e138">Supported</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d41398e141">Example</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Supported" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e138 ">
              <p style="margin-bottom:0;">Boolean Field Values</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e141 ">
              <p>For a boolean field, that is, a field where the only options are true or false, natural
                language search only supports English-defined values.</p>
              <p style="margin-bottom:0;">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.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Supported" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e138 ">
              <p style="margin-bottom:0;">Date</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e141 ">
              <p>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.</p>
              <p style="margin-bottom:0;">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 <a href="https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_select_dateformats.htm" target="_blank">Date Formats and Date Literals</a> in the SOQL
                and SOSL Reference guide.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Supported" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e138 ">
              <p style="margin-bottom:0;">Operators</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e141 ">
              <p>Search doesn’t translate the operators "top" and "my", but you can combine these
                operators with non-English words.</p>
              <p style="margin-bottom:0;">Example: The query my casos (Spanish) is a valid query, but mis casos isn’t.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Supported" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e138 ">
              <p style="margin-bottom:0;">Stopwords</p>
            </td>

            <td data-label="Example" class="slds-cell-wrap" style="vertical-align:top;" headers="d41398e141 ">
              <p style="margin-bottom:0;">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.</p>
            </td>

          </tr>
        </tbody>
      </table>