Searching translated content

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Searching Translated Content

    The ServiceNow AI Platform® enables users to search translated content effectively, categorizing it into translated fields and translated documents. Understanding how AI Search operates with these two content types is essential for maximizing search accuracy and relevance in your ServiceNow environment.

    Show full answer Show less

    Key Features

    • Translated Fields: AI Search matches and displays translations in the user's session language. If a translation is unavailable, it defaults to the English version. Note that this does not apply to the Knowledge [kbknowledge] table, where translated fields are not matched or displayed.
    • Reindexing: After inserting or updating translations in the Translated Text [systranslatedtext] table, reindexing is necessary to apply these changes in AI Search results.
    • Translated Documents: Searches are restricted to documents in the user's session language by default. However, starting from the Utah release, you can configure filters for globally searchable knowledge articles, allowing cross-language matching.
    • Fallback Languages: Since the Tokyo release, you can configure a fallback language for each session language, enabling results in both the session and fallback languages. A global fallback locale can also be set for broader document matching.

    Key Outcomes

    By understanding and applying these features, ServiceNow customers can enhance their search capabilities, ensuring that users access relevant translated content effectively. Proper configuration of fallback languages and global search settings can significantly improve the user experience across multiple languages.

    Understand how AI Search searches translated fields and documents.

    The ServiceNow AI Platform® includes two categories of translated content:
    1. Translated fields, such as translations of Catalog Item record fields.
    2. Translated documents (long text and HTML values), such as translations of knowledge article records.

    The default AI Search matching behavior differs for these two types of content.

    Translated fields

    When you search content that includes translated fields, AI Search matches and displays field translations in your ServiceNow AI Platform session language. If a field lacks a translation in the session language, AI Search instead falls back to matching against the English-language field value. For example, if your session language is Japanese, AI Search returns Japanese field translations where present on a Catalog Item record, but returns English values for Catalog Item fields that have no Japanese translation.

    To learn more about how the ServiceNow AI Platform handles translated fields, see Translating individual UI strings.

    If you insert or update field translation records in the Translated Text [sys_translated_text] table, reindex content from the relevant indexed source to make AI Search use the new translations. For details on reindexing content, see Perform a full table index or reindex for a single AI Search indexed source and Perform a full table index or reindex for multiple AI Search indexed sources.
    Note:
    AI Search doesn't support translated fields on the Knowledge [kb_knowledge] table. This behavior has the following effects.
    • Search queries don't match translated versions of kb_knowledge translated fields.
    • Search results don't display translated versions of kb_knowledge translated fields.
    • Search application facets don't display translated versions of kb_knowledge translated fields.

    Translated documents

    When searching content with translated documents, by default AI Search only matches documents in the user's ServiceNow AI Platform session language. For example, a Japanese user search only matches knowledge articles in Japanese, excluding all knowledge articles in other languages.

    Starting in the Utah release, you can configure a filter condition for globally searchable knowledge articles. Articles that satisfy this condition can be matched by searches in any language. For information on this setting, see Configure globally searchable knowledge articles.

    Beginning in the Tokyo release, you can set a fallback language for each language enabled in your ServiceNow AI Platform instance. When a fallback language is configured for the user's session language, AI Search returns search results in both languages. For more details, see AI Search interaction with fallback languages.

    You can configure a global fallback locale to make AI Search match documents in the instance locale's language as well as the user's session language. This configuration works best when you want to make all English-language documents globally searchable. To learn more about configuring a global fallback locale, see Enable a global fallback locale for translated content.