Limitations of Multi-Language Suppor...

TL;DR Opening

Starting in NetSuite 2026.1, the multi-language feature in Field Service Management (FSM) has notable limitations. Specifically, language translations are not fully supported, which can affect usability and customization for users operating in different languages.

What's New in Multi-Language Support for FSM

While the option to conduct testing for translation functionality exists, it's crucial for developers and administrators to understand the limitations surrounding this feature:

Key Limitations

Language Translations: Currently, NetSuite does not support full translations of FSM. Users can add translation strings to a custom translation collection (custcollection_fsm) or create their own for custom records and fields.
Scheduler and Mobile Settings: The language preference set in NetSuite only impacts FSM fields. For elements like dates, times, and numbers on the scheduler board or mobile app, the browser's language setting is used instead.
Transportation Map Layers: Labels for various transportation routes on map layers cannot be translated.
Reports and Notifications: FSM reports, email notifications, and scripted strings are not translatable. Scripted strings are dynamic text generated for notifications and templates.
Custom FSM Record Limitations: If you have introduced any custom records, lists, or forms, these will not be automatically translated. Manual translations for these customizations are required.

Testing Translation Functionality

To explore the translation capabilities in FSM, consider the following steps:

Add strings to the FSM translation collection to test.
Create a custom translation collection for your specific records and configurations.
Reference your custom translations during setup.

For a detailed guide on testing translations within FSM, reach out to NetSuite Customer Support for assistance.

Who This Affects

This update primarily impacts:

Administrators: Managing language settings and customizations.
Developers: Working with custom record translations and scripted strings.
Field Service Management Users: Affected by translation limitations in reports and the mobile app.

Key Takeaways

Multi-language support in FSM is limited; full translations are not available.
Browser language settings influence date and time format rather than NetSuite settings.
Custom records require manual translation work; automation is not provided.
Important aspects such as map labels and scripted notification strings are unsupported in translations.
Testing translation requires building custom collections and consulting support for guidance.

Frequently Asked Questions (4)

Does the multi-language support in FSM affect custom record translations?

Yes, custom records, lists, and forms in FSM require manual translations as they are not automatically translated by NetSuite.

What happens to the display of dates and times in FSM when using multi-language support?

The language preference set in NetSuite only influences FSM fields; for dates, times, and numbers, the browser's language setting is utilized instead.

Are any reports or notifications in FSM translatable under the new multi-language support?

No, FSM reports, email notifications, and scripted strings are not translatable, meaning that dynamic text for these elements remains in the default language.

Is there a feature flag that needs to be enabled for multi-language testing in FSM?

The article does not mention a specific feature flag; however, testing multi-language functionality involves adding strings to the translation collection and creating custom translation collections.

Limitations of Multi-Language Support in NetSuite 2026.1