Configuring FSM Localization and Translation

Configure language selections, browser formatting, and translation references for FSM Mobile labels and customer-facing output. For the language-selection rules, translation lifecycle, and scope of supplied-record maintenance, see FSM Localization and Translation.

Before You Begin

Before you change language or translation settings, complete the following prerequisites:

Use a role that can change the applicable account settings, employee or customer records, and Field Service Configuration. Creating or changing translation collections requires Manage Translation permission. See Translation Collections Prerequisites.
Enable Multi-Language when employees or customers need separate language selections, or when you manage custom translation collections. Add the required translation languages to the account's supported-language list.
For FSM Mobile text, identify the existing resource and element IDs. For template text, identify the file that contains the text. For custom text, obtain the collection ID, string keys, and translations for each intended language.
Synchronize outstanding work before refreshing or signing out of FSM Mobile.

Default Configuration and Choices

FSM supplies translation references for standard labels and templates in custcollection_fsm. Standard translations are included with FSM releases from 2026.03.1. No manual import is required. The supplied collection uses English (US) strings for English variants and is locked. Use a separate collection for custom text. See 2026 FSM Release Notes.

Language choices and browser formatting are separate settings. Use the following controls for the intended outcome.

Outcome	Setting and Location	Applicable Default or Fallback
Enable employee and customer language selection	Multi-Language box on the Company subtab, under International, on the Enable Features page (Setup > Company > Setup Tasks > Enable Features).	Without this feature, FSM Mobile and notification language selection use the account's default language. Browser formatting remains independent.
Set FSM Mobile label language	Employee record, Field Service > Field Service Language, `custentity_fsm_language`.	A blank field uses the account's default language. Applies when Multi-Language is enabled.
Set customer notification and report language	Customer record, Field Service > Field Service Language, `custentity_fsm_language`.	A blank field falls back to the related subsidiary language, when supplied by the notification context, then the account's default language. Applies when Multi-Language is enabled.
Set employee notification language	Employee record, Field Service > Field Service Language, `custentity_fsm_language`.	With Multi-Language enabled, a blank field uses the first available language from the related subsidiary and account default. FSM checks the subsidiary only when the notification has subsidiary context.
Review the subsidiary fallback	Related subsidiary's Language field, `languagelocale`, at Setup > Company > Subsidiaries.	Used only when the notification has subsidiary context and no applicable employee or customer language. This is also a NetSuite setting with wider effects.
Set Schedule Board configuration language	Language field under Localization on General (Home > Set Preferences).	Uses the current NetSuite language preference. The Schedule Board reads it independently of the Multi-Language check used by FSM Mobile.
Set supported date, time, and number display formats	Browser or device language preference.	Uses the browser language for the controls described in Configure Browser Formatting.
Translate custom FSM Mobile text	Existing resource `label`, or element `label` and `placeholder`, under the literal `"routes/mobile"` configuration property.	Existing standard or form-generated text applies unless overridden. A literal override remains literal. A collection reference resolves available translations.

Outcome

Setting and Location

Applicable Default or Fallback

Enable employee and customer language selection

Multi-Language box on the Company subtab, under International, on the Enable Features page (Setup > Company > Setup Tasks > Enable Features).

Without this feature, FSM Mobile and notification language selection use the account's default language. Browser formatting remains independent.

Set FSM Mobile label language

Employee record, Field Service > Field Service Language, custentity_fsm_language.

A blank field uses the account's default language. Applies when Multi-Language is enabled.

Set customer notification and report language

Customer record, Field Service > Field Service Language, custentity_fsm_language.

A blank field falls back to the related subsidiary language, when supplied by the notification context, then the account's default language. Applies when Multi-Language is enabled.

Set employee notification language

Employee record, Field Service > Field Service Language, custentity_fsm_language.

With Multi-Language enabled, a blank field uses the first available language from the related subsidiary and account default. FSM checks the subsidiary only when the notification has subsidiary context.

Review the subsidiary fallback

Related subsidiary's Language field, languagelocale, at Setup > Company > Subsidiaries.

Used only when the notification has subsidiary context and no applicable employee or customer language. This is also a NetSuite setting with wider effects.

Set Schedule Board configuration language

Language field under Localization on General (Home > Set Preferences).

Uses the current NetSuite language preference. The Schedule Board reads it independently of the Multi-Language check used by FSM Mobile.

Set supported date, time, and number display formats

Browser or device language preference.

Uses the browser language for the controls described in Configure Browser Formatting.

Translate custom FSM Mobile text

Existing resource label, or element label and placeholder, under the literal "routes/mobile" configuration property.

Existing standard or form-generated text applies unless overridden. A literal override remains literal. A collection reference resolves available translations.

The supplied Field Service Language record, customrecord_fsm_language, provides the Field Service Language choices. A displayed choice does not establish that every custom label or output has a translation.

Portuguese (Portugal), pt_PT, has an additional release condition. The 2026.07.1 release notes describe translations as available for accounts in Portugal with Portuguese (Portugal) as the default language. Check the installed release and account conditions before relying on that locale.

Enable Language Selection and Translation Entry

To enable language selection and translation entry:

Go to Setup > Company > Setup Tasks > Enable Features.
On the Company subtab, under International, check Multi-Language, then click Save.
For custom translation entry, add the required languages:
1. Go to Setup > Company > General Preferences.
2. Click the Languages subtab.
3. Select a required translation language and click Add. Repeat for each language you need to add.
4. Click Save.
See Enabling the Entry of Translation Strings for a Specific Language.

Adding a language makes it available for translation entry. You must still supply the custom strings and translations used by your configuration.

Set Employee and Customer Languages

To set employee and customer languages:

Edit the employee record for the technician or the employee associated with the notification.
On Field Service, select a language in the Field Service Language field and save the record. The selected language controls FSM Mobile labels and employee notifications when Multi-Language is enabled. The selected language also affects prompt selection in Enhanced Technician Notes. See How Technician Language Affects Enhanced Technician Notes.
For task, case, or project task notifications and their template-generated report attachments, edit the associated customer record. On Field Service, select a language in the Field Service Language field and save the record.
If you intend to use subsidiary fallback, review the related subsidiary's Language field before leaving the employee or customer field blank. For the wider setting, see Creating Subsidiary Records.

Note:

Changing the recipient list does not select a separate language for each recipient. Service notifications use the related customer and subsidiary context. Employee notifications use the employee and subsidiary context.

For FSM Mobile emulation, check the emulated employee's language. The administrator's own language is not the emulated employee's selection.

Set the Schedule Board Language Preference

To set the Schedule Board language preference:

Go to Home > Set Preferences.
On General, under Localization, select a language in the Language field and save.

This user preference does not set the technician's Field Service Language or the customer's notification language.

Configure Browser Formatting

Set the preferred language in the browser or device settings used to run FSM. Apply the change using that browser's instructions, then reopen the application and inspect the affected controls.

The following table lists the controls and values to check.

Control	Values to Check
FSM Mobile date, time, and date/time elements	Input segments and read-only date/time values.
FSM Mobile number elements	Displayed number values.
Schedule Board date filters	Days before and days after values.
Schedule Board settings panel	Start and end hour values.

Control

Values to Check

FSM Mobile date, time, and date/time elements

Input segments and read-only date/time values.

FSM Mobile number elements

Displayed number values.

Schedule Board date filters

Days before and days after values.

Schedule Board settings panel

Start and end hour values.

Changing an employee's language can change translated labels, but these formats continue to follow the browser language. These formatting paths do not require Multi-Language to be enabled. Locale presentation can differ between browsers and devices.

Configure Translated Custom Mobile Labels

Use a separate translation collection and override the text on the existing resource. Retain its resource ID, element IDs, record mappings, resource-selection rules, and validation settings.

To configure translated custom FSM Mobile labels:

Go to Customization > Translations > Manage Translations. On Collections, click Create New. Complete Name, ID, and Default Language, then click Save. The default language cannot be changed after saving. See Managing Translation Collections.
On Collections, find the collection you want to update. In the Strings column, click +. Supply the source text, key, description, and available translations, then save. See Adding Strings to Translation Collections. For bulk translations, use Importing Translations into a Translation Collection.
Record the collection's full script ID and each string key.
Prepare an inactive copy of the current configuration before editing:
1. Go to Field Service > Administration > Configuration. The Field Service Configuration page opens the active configuration record.
2. Record the name of the active configuration so that you can identify it when activating the replacement.
3. In Name, enter a unique name for the new version. Begin with the current product version, followed by the date in YYYYMMDD format and your initials. You can add a short description.
4. Check the Inactive box to keep the replacement inactive during editing.
5. From the Save list, click Save As.
6. Click List. On the Field Service Configuration List page, check the Show Inactives box.
7. Find the new record and click Edit.
In the inactive configuration revision, replace the intended label text with collection_ID.KEY, using your collection's full script ID and string key. A reference is plain text in the JSON string. It does not need a ${ ... } template tag.
In the following example, custcollection_fsm_custom is an illustrative customer-owned collection. Create it, or replace the ID with your collection's actual script ID. Add JOB_DETAILS and ACTIONS_TAKEN with source strings and the required translations.

This JSON fragment changes the tab label and one field label on the existing details resource. Merge it into the existing configuration. For JSON terminology, see Understanding the Hierarchy.
```
                    {
  "routes/mobile": {
    "details": {
      "label": "custcollection_fsm_custom.JOB_DETAILS",
      "element": {
        "actions": {
          "label": "custcollection_fsm_custom.ACTIONS_TAKEN"
        }
      }
    }
  }
} 

                  
```
Use this example only when details is selected for the relevant jobs. Standard configuration supplies its tab label through custcollection_fsm.app_detailstab_name and the actions label through custcollection_fsm.app_detailstab_actions_taken_name. The fragment retains the existing mapping of actions to custevent_nx_actions_taken, together with the resource's other inherited settings.
For a resource generated from a NetSuite form, use the actual generated field ID in element. An explicit label overrides the generated label. Changing this FSM Mobile label does not rename the NetSuite field. See Form Properties and FSM Mobile Element (Block) Reference.

Normally omit a locale suffix so the reference follows the language selected for the request. A reference such as custcollection_fsm_custom.ACTIONS_TAKEN.fr_FR selects that locale for the reference. Use a fixed locale only when that text is intentionally independent of the employee or customer selection. Shared expression and template-tag guidance is in FSM Expressions and Template Tags.

Important:
A label override does not require creating a resource. Copying a standard resource under another ID is a separate customization. Do not assume that the copy retains the original resource's server synchronization or processing of related records.

Standard default JSON for these two labels (language selection itself is an account or record setting):
```
                  {
  "routes/mobile": {
    "details": {
      "label": "custcollection_fsm.app_detailstab_name",
      "element": {
        "actions": {
          "label": "custcollection_fsm.app_detailstab_actions_taken_name"
        }
      }
    }
  }
} 

                
```
Check the Editor content for valid JSON before saving.

FSM checks whether the Editor content can be parsed as JSON. When Preview is enabled, the form displays an indicator that shows whether the JSON is valid or invalid. Saving rejects invalid JSON whether Preview is enabled or disabled. Repeated property names within one object pass the syntax check, but only the last value remains. With Preview enabled, the Editor can remove an earlier duplicate when you finish changing the field. Saving removes it in either mode. The check also does not comprehensively validate property paths, values, record references, searches, expressions, or the account setup needed for the intended behavior.

Valid JSON and Configuration Preview do not establish that a property is supported or that downstream processing succeeds.
From the Save As list, click Save.
On the configuration list, clear the Inactive box for the replacement record and check the Inactive box for the previous active record.
Click Submit. Reopen the configuration page to confirm the intended record is active.

Use Translated Text in Emails and Reports

Use the same collection references for custom text in the applicable HTML email or XML report template. For example, this template fragment inserts the available translation for one label:

            <p>custcollection_fsm_custom.ACTIONS_TAKEN</p>

Preserve the existing template's data references and rendering structure. FSM resolves collection references before FreeMarker processes the template. Literal text without a reference remains literal.

Configure template files and their data using Configuring Email Content and Language and Translations. These topics explain how to set up emails and reports. The selected notification language is passed to the email and its template-generated report attachments. Attaching an existing file does not render or translate that file again.

When Language Changes Apply

Changed language settings and configuration apply to subsequent applicable requests and output generation. These changes do not regenerate previous emails, PDFs, or record names.

Refresh FSM Mobile for changed labels. Changes to built-in FSM Mobile interface messages can require signing out and signing in again. Browser-format preferences remain independent of the employee's Field Service Language.

An unresolved translation key can remain visible. Do not assume that FSM uses English as a fallback if a translation collection fails to load. Scheduled language processing updates translated names on selected supplied records when Multi-Language is enabled, rather than supplying every possible translation or locale. See FSM Localization and Translation and FSM Script Reference.

For performance measurement and data capture, see FSM Performance and Data Collection.

Changing Language and Translation Settings

Clear the Field Service Language field on an employee or customer record to use the applicable account or subsidiary fallback. Disabling Multi-Language changes FSM language selection. Browser-controlled formatting remains unchanged.

Removing custom label or template overrides restores their inherited definitions. Existing emails, PDFs, and stored names remain unchanged.

General Notices