Globalization Enhancements in Field Service Management 2026.1
2026.1 introduces globalization enhancements for Field Service Management, including translation support and issue fixes.
TL;DR Opening
Starting in NetSuite 2026.1, the Field Service Management (FSM) SuiteApp introduces globalization enhancements and several critical issue fixes. This release improves the overall performance and usability of FSM, making it easier to manage service tasks across diverse language settings.
What's New
Globalization Enhancements
- Translation Support: Scripted strings, reports, and notifications in FSM are now prepared for future translation support. Although other languages are not yet visible in scripted strings or reports, this update sets the groundwork for a comprehensive multi-language experience. To participate in early testing, contact your NetSuite Account Manager for resources, including a PDF guide and test files.
Issue Fixes
- Improved Barcode Scanning Reliability: The scanning function within the FSM Mobile application now delivers enhanced performance. It optimizes resolution depending on the device to ensure accurate readings even in poor lighting conditions or awkward angles.
- Fixed CSV Import for Employee Passwords: This release resolves issues where employee passwords for mobile users could not be set or updated via CSV import. The Field Service Password field is now processed properly.
- Error-Free Password Entry in Employee Records: Users can save passwords for mobile-only employees without receiving erroneous alerts. The save functionality works smoothly on the first attempt, offering a more reliable user experience.
- Accurate Search Results for Dynamic Option Fields: This update resolves issues where dynamic option select fields were returning inaccurate or incomplete search results, ensuring better functioning.
- Correct Latitude and Longitude from Assets Without Addresses: Latitude and longitude values are now correctly copied from related assets, even in the absence of an address, which adds critical geographic accuracy to new tasks.
- Consistent App Icon Background on Mobile Home Screens: The app icon will maintain a consistent background appearance across mobile home screens.
Who This Affects
- Roles Impacted:
- Administrators
- Field Service Managers
- Mobile Users
- Developers
Key Takeaways
- Translation support lays the groundwork for future multi-language functionalities in FSM.
- Enhancements in barcode scanning significantly improve its reliability for users.
- CSV import processes for employee passwords and error notifications have been resolved, boosting user experience.
- Geographic accuracy is improved for project tasks through better handling of asset location data.
Frequently Asked Questions (4)
Is the translation support for Field Service Management available immediately in NetSuite 2026.1?
No, the translation support is not immediately available. Scripted strings, reports, and notifications are prepared for future translation support, but other languages are not yet visible.
What improvements have been made to barcode scanning in this release?
The barcode scanning functionality in the FSM Mobile application has been enhanced. It now optimizes resolution based on the device to ensure accurate readings, even in poor lighting conditions or awkward angles.
Can employee passwords for mobile users be updated via CSV import in the 2026.1 release?
Yes, the 2026.1 release resolves issues with setting or updating employee passwords for mobile users via CSV import. The Field Service Password field now processes these updates properly.
How does the update affect latitude and longitude data handling in FSM tasks?
The update ensures latitude and longitude values are correctly copied from related assets, even when there is no address present, which improves geographic accuracy for new tasks.
Weekly Update History (1)
Field Service Managementupdated
Updated the 2025.10.3 Release Notes to list issue fixes in reverse chronological order.
View Oracle DocsSource: 2026.01.1 Release Notes — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.
Was this article helpful?