Set Up a Multi-Language Form

With the Multi-Language feature, you can create a single form and provide it to your field users in multiple languages. It’s simple to set up a Multi-Language FormClosed A Multi-Language Form is a form that’s set up with different translations so that field users can choose their preferred language. Translated content includes page and section names, question text, help text, and other form content. and an associated output Document. Simply download Excel files that contain the strings to translate, add translations, upload the files, and activate the languages. This topic describes the steps to set up a Multi-Language Form.

Tip:You can set up an existing form with multiple languages—you don’t have to create a new form.

Available as an add-on to the Advanced and Enterprise tiers:

Advanced +Add-on
Enterprise +Add-on



Tip:The Form Builder supplies a default Unique IDClosed A Unique ID refers to the specific identifier of a question, form page, form section, or Data Destination. Unique IDs are used as reference points when pulling data for conditional logic, Analytics projects, Data Destinations, and Documents. when you add a page, section, question, answer exception, or other element to the form. We recommend that you change these to IDs that will help you easily identify these elements in the translation files. The following example shows how a translation file displays the unique IDs in the key_name column.

key_name column that shows the UniqueIDs "Site Information", "Job Information", and "Inspection Date" for a page, section, and question.

Steps to set up a Multi-Language Form

  1. From the Manage Forms menu, create or edit a Mobile App form.

    • To create a new form:

      Manage Forms > Create New Form > Build a Mobile Form

      Enter a name and description, and then save the form.

    • To edit a form:

      Manage Forms > List Forms > FormName > Edit Form

      where FormName is the form that you want to edit.

    Tip:You can choose a new or existing form; you don’t have to build a new one.

  2. Go to Settings > Form Information.

  3. In the Languages section, select Enable multiple languages.

    Result: The Languages section expands to display additional setup options.

    Language section that shows additional languages enabled, with Spanish selected, the download and upload buttons visible, and the "Active" checkbox selected.

  4. Select the language that the form is built in (the source language). The system uses this language to generate the strings for translation.

    Tip:The source language is also the fallback language for any missing translations.

  5. In the Additional Languages section, select a language from the list.

  6. Select Download to get an Excel file that contains the translation strings for all translatable form content.

    Result: The system generates a translation file (.xlsx) that contains all translatable text in the form.

    The translation file has the structure shown in the following illustration.

    Excel file that shows the following columns: key_name, en (source language used by the Form Designer to build the form), es (language added by the Form Designer), changes_occurred (to indicate when a source string changed after file upload), and comments (for messages to your translator).

    Info:The topic How Multi-Language Translation Files Work: Translation file details provides guidelines and tips for working with the translation files.

  7. Add comments for your translator (optional) to provide more information about a translation string. For example, you could provide the translator with synonyms to make the meaning clear. Send the file for translation.

  8. Once the translation file is complete, Upload the file. To make the form available to your field users in the additional language, set the language to Active.

    Note:To upload the translation files successfully, you must keep all five column headings exactly the same as in the downloaded file.

  9. Repeat steps 5-8 for each additional language up to a maximum of 10, and then Save and Deploy the form.

    Result: The system creates a new form version.

    Note: Users must reconcile to get the new form version.

    Test your output documents to make sure the results are what you expected.

    Info:You can set up a PDF, Microsoft Word, or HTML output document for translated content and link it to the form. The topic Steps to Set Up Translations for a Multi-Language Document describes this procedure in detail.

Options-based question translations

An options-based question is a question that displays a list of options as possible answers. The list can come from a Data SourceClosed Data sources, also known as "Lookups", are external sources of data that you upload or connect to TrueContext. You can reference this data in a form to populate answers or answer options. Data sources save typing, reduce errors, and make it easy to provide mobile users with only the relevant, most current data., or you can manually define the list. We use the term lookup to describe a question that gets a list of options from a Data Source.

Manually-defined options

When you set up an options-based question, you can specify different values for the Value submitted to server and the Text displayed on device. You can translate the display value (but not the server value). When a field user, dispatch, or App‑to‑App call selects a language, the form shows the translated display value.

Data Source options

A Data Source provides a list of options for a lookup question. You can set up the lookup question to display translated values in the form.

Info:We store Data SourcesClosed Data sources, also known as "Lookups", are external sources of data that you upload or connect to TrueContext. You can reference this data in a form to populate answers or answer options. Data sources save typing, reduce errors, and make it easy to provide mobile users with only the relevant, most current data. as tables (rows and columns) in the TrueContext system. To set up translated values in your Data Source, you must have a column that contains a language code for each row. The topic Data Source Translations describes in detail how to set up translations in a Data Source.

The following example describes how to set up a lookup question for translations.

Question options that show "Use Data Source for Options" selected, the "Multi-Language" switch toggled to on, and the "Select the language column..." set to “Language”. The language column in the data source contains a language code for each translated row.

When the user, dispatch, or App‑to‑App call selects a language, the form displays the translated values from the Data Source.

Tip:You can translate both the display and the data (server) values in your Data Source. The translated values are sent to the server when the user submits the form.

Conditional logic rules that use selected language

You can set up a Conditional Logic rule that’s based on the selected language.

The following example describes how to set up a condition that uses a selected language.

A Conditional Logic rule that shows an “If” statement condition set to “Selected Language” “Is” “French”. The “Then” action is set to show “RTU Diagram (FR)” and hide “RTU Diagram (EN)” and “RTU Diagram (ES)”.

Note:When you build the condition, you can only select languages that you set up in the form settings.

In this example, the Form Designer has an HVAC diagram with labels in different languages. They want to show only the diagram that has labels in the selected language and hide the other translations from the user. They create other rules to do the same for the English and Spanish diagrams.

Info:If you want to include other languages as “Or” conditions, you can select more than one language in the same condition. The topic Building Conditional Logic Rules describes in detail how to set up condition sets that use “And” and “Or”.