FSM SuiteApp Now Supports Multi-Language via custcollection_fsm Translation Collection

What Changed

The FSM SuiteApp now participates in NetSuite's Multi-Language framework. When the Multi-Language feature is enabled at Setup > Company > Setup Tasks > Enable Features > Company > International, FSM fields rendered inside the NetSuite UI will respect each user's language preference (set at Home > Set Preferences > General > Localization > Language). Locale-sensitive formatting for dates, times, and numbers on the scheduler board and mobile app follows the browser's locale, not the NetSuite user preference — these are two different settings and will diverge if they don't match.

Translation Mechanism

FSM ships a built-in translation collection: custcollection_fsm. You can add translation strings to this collection to test or extend translations for standard FSM fields. For any custom records, fields, or forms you've added to FSM beyond the bundled SuiteApp components, you must create your own translation collection and reference those translations in your configuration — they will not be picked up automatically.

Current Limitations

Oracle's documentation explicitly flags these gaps — treat them as hard blockers before relying on this in production:

• No actual language translations ship yet. The framework is enabled, but Oracle has not delivered translated strings. You can test by adding your own strings to custcollection_fsm.
• Scheduler & mobile use browser locale, not NetSuite locale. The NetSuite language preference only governs FSM fields inside the core NetSuite UI. The scheduler board and mobile app read the browser's Accept-Language / device locale for date, time, timezone, and number formatting.
• Reports, email notifications, and scripted strings are not translatable. Any text generated dynamically via SuiteScript or used in notification templates remains English-only.
• Map transportation layers are not localizable. Labels on roads, highways, railways, shipping/airline routes stay in their default language.
• Custom FSM components require manual translation. Anything you added beyond the stock SuiteApp — custom records, lists, forms — needs its own translation collection with explicit string mappings.

What to Do

1. Enable the feature if you want to begin testing: Setup > Company > Setup Tasks > Enable Features → Company subtab → International section → check Multi-Language → Save.
2. Set user language preferences per user: Home > Set Preferences → General subtab → Localization → select Language → Save. This is per-user and does not affect other accounts.
3. Audit your FSM customizations. If you've added custom records, fields, lists, or forms to the FSM SuiteApp, inventory them now. Each will need its own translation collection with mapped strings before they'll render in non-English locales.
4. Test with custcollection_fsm. Add sample translation strings to the FSM translation collection and verify they render correctly in the NetSuite UI. Oracle suggests contacting NetSuite Customer Support for a PDF testing guide.
5. Do not depend on translated reports or notifications. Any workflows that send FSM email notifications or generate FSM reports will remain English-only for now. Plan accordingly if you're rolling this out to non-English users.
6. Align browser locale with NetSuite locale for field technicians using the scheduler or mobile app, or accept that date/time/number formatting may differ between the NetSuite UI and the scheduler/mobile views.

Open Questions

The source does not specify which NetSuite release introduced this capability, nor does it provide a timeline for when full language translations, report localization, or scripted-string translation will ship. If you're planning a multilingual FSM rollout, confirm the current state of delivered translations with NetSuite Support before committing to a go-live date.