---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Export and edit translation records

# Export and edit translation records {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Export translation records to translate to additional languages in your preferred translation environment and import the new or edited translation records through import sets.

## Before you begin

Note:  
Using the Localization Framework application is recommend for translating to an unsupported language or translating large amounts of custom UI string content in a supported language. For more information, see [Localization Framework](https://servicenow-prod.fluidtopics.net/hWWbjrWLsHsFZGw_lOf5Hw "The ServiceNow Localization Framework application standardizes and enhances the translation process of artifacts across the platform through configurable workflows. Such artifacts include ServiceNow Service Catalog items, Virtual Agent topics, Natural Language Understanding models, and Document Templates of ServiceNow HR Service Delivery.").

Role required: admin

## About this task

In the following cases, translate strings in the UI outside of the ServiceNow AI Platform and import them through import sets:  
* You have a significant amount of customer-created UI components and you want to translate these components into other languages.
* You want to modify translations that ServiceNow provides in internationalization plugins.
* You want to translate an instance into a language that ServiceNow does not support with internationalization plugins. For more information, see [Translating to an unsupported language](https://servicenow-prod.fluidtopics.net/8pd1J9fmPPy9Yf9eLa8p4A "Translate the interface of an instance to a language for which ServiceNow does not provide an internationalization (I18N) plugin.").
{#t_TranslateTheInterface__ul_flw_knb_vhb}

All translatable UI strings items are stored in translation table records. The only time you would translate UI directly in translation records is when you have a small amount of customer-created UI components and you know
exactly where they are. For more information about translation tables, see [Translation tables](https://servicenow-prod.fluidtopics.net/q6IL8QaIYEPLD_k3arJ7xw "ServiceNow stores translation information in these tables.") and [Translating individual UI strings](https://servicenow-prod.fluidtopics.net/ph9_UxsnphjyKQfy6c8NOw "When translating just a few UI strings, such as when you add customizations to a translated instance, use the procedure that applies to the type of text being translated.").

## Procedure

1. If you are translating customer-created UI components, locate the translatable strings.  
   For more information, [Locating translatable UI strings](https://servicenow-prod.fluidtopics.net/FiWciIyq0d8JwqSnbSmTQw "Locate individual untranslated strings to provide your own translation of customer-created and customer-edited strings, such as field names and messages.").
2. Export the relevant translation table records into a format (such as Excel) that can be easily manipulated.  
   For more information about exporting a list of records, see [Export data from a list](https://servicenow-prod.fluidtopics.net/i7sDpMe8BxnzsKw~YbJXxg "Export a list of records to a variety of file formats.").
3. Within the exported document, translate the following fields in each row, depending on the translation table:  
   {#t_TranslateTheInterface__table_n5x_nv2_d3b__entry__2}

   | Translation table | Fields to translate |
   |-|-|
   | Field Labels | Label, Plural, Hint |
   | Translated Name/Field | Label (translate) |
   | Message | Message |
   | Choices | Label |
   | Translated Text | Value |
   [ ]

   {#t_TranslateTheInterface__table_n5x_nv2_d3b}
4. Within each row, change the "Language" column to the [BCP 47](http://www.iana.org/assignments/language-subtag-registry/language-subtag-registry) code of the new language.  
   In Translated Text and Message records, type the full name of the language instead of the BCP 47 code.
5. Save your changes.

## What to do next

Import the translated document back into the instance as an import set.

## Import a translation from an Excel spreadsheet {#ariaid-title2}

The System Import Sets application contains import tables and corresponding transform
maps to assist with importing translations from an Excel spreadsheet.

### Before you begin

Role required: admin

### Procedure

1. Navigate to AllSystem Import SetsLoad Data.
2. Select Use Existing and the Table name that matches the type of data being imported, as follows.  
   * For choices, select the `[u_sys_choice]` table.
   * For field labels, select the `[u_sys_documentation]` table.
   * For translated names and fields, select the `[u_sys_translated]` table.
   * For messages, select the `[u_sys_ui_message]` table.
   * For translated text, select the `[u_sys_translated_text]` table.
   {#t_ImportATranslationFromExcel__ul_hjr_bmr_zp}
3. Select Upload an Excel file, and then click Browse to select the source Excel spreadsheet.
4. If appropriate, specify the Work sheet and Header row number.
5. Select Go.  
   The translations are now available in the appropriate Import Set Table.
6. Navigate to AllSystem Import SetsTable Name and review the imported information to verify that the import was successful.
7. To transform the imported data into the corresponding table, navigate to AllSystem Import SetsRun Transform.
8. Select the appropriate transform map, as follows.  
   Note:  
   Make sure you choose a transform map that has the Run Business Rule option selected. If the transform map does not have this option selected, any customized translations you have may be overwritten during the next upgrade.  
   * For choices, select the Sys Choice Translation Map.
   * For field labels, select the Sys Documentation Translation Map.
   * For translated names and fields, select the Sys Translated Translation Map.
   * For messages, select the Sys UI Message Translation Map.
   * For translated text, select the Sys Translated Text Translation Map.
   {#t_ImportATranslationFromExcel__ul_a2l_3nr_zp}
9. Select Transform.

*[\>]: and then