FSM 2026.01.1: Translation Scaffolding and Mobile/Script Bug Fixes

This is a Field Service Management (FSM) maintenance release. There are no SuiteScript API, record schema, or REST endpoint changes documented. The notable items are translation scaffolding and a batch of issue fixes affecting FSM Mobile, the Employee record, dynamic select fields, Task/Project Task geocoding, and a contact-attachment scheduled script.

What changed

Globalization scaffolding

Scripted strings, reports, and notifications in FSM are now structurally ready for translation, but no additional languages are exposed yet. Selecting a non-English language will still render English. Oracle says full translation files ship in a future release; testing is gated behind your Account Manager and a separate PDF guide plus test files.

Issue fixes

• FSM Mobile barcode scanner: The scanner now auto-selects an optimal capture resolution and is more tolerant of poor lighting and angles across all supported symbologies. No API surface change — this is a runtime behavior fix in the mobile client.
• CSV Import — Employee passwords: The Field Service Password field on the Employee record is now processed correctly during CSV Import for mobile-only users. Previously, imports targeting this field failed.
• Employee record password entry: Saving a password on a mobile-only employee record no longer throws a spurious Please enter a password validation error on the first save.
• Dynamic option select fields: Searches against select fields configured with dynamic options now evaluate against the current option list, fixing cases where results were missing or empty due to a stale option set.
• Task / Project Task geocoding: When a Task or Project Task is created from an Asset, latitude and longitude are now copied from the Asset even when the Asset's address field is blank. Previously, missing address text suppressed the coordinate copy.
• Mobile app icon: The home-screen icon renders with a solid blue background on iOS and Android, with no stray badges or transparency artifacts.
• iOS PWA launch: Launching from the iOS home screen now opens full-screen (no Safari chrome) and displays the app name as Field Service.
• Contact attachment scheduled script: The scheduled script that attaches customer contacts to a project no longer loops when the customer has more than 1,000 contacts. It now attaches all contacts and clears the Update Contacts checkbox in a single successful run. If you have customers with large contact volumes, this is the most operationally significant fix in the release.

What to do

1. If you previously built CSV Import templates for mobile-only employee onboarding and worked around the Field Service Password failure (e.g., by setting passwords manually post-import), you can now consolidate that step back into the import.
2. Re-test any saved searches or scripts that filter on dynamic-option select fields — if you added defensive logic or cache busts to compensate for the stale-options bug, you can likely remove it.
3. If you maintain custom geocoding workarounds on Task/Project Task creation from Assets, verify whether the standard copy-from-Asset behavior now satisfies your case and retire the workaround.
4. For any customer with >1,000 contacts, re-run the contact attachment scheduled script and confirm the Update Contacts flag clears as expected. If you forked or replaced this script with a custom Map/Reduce due to the looping bug, evaluate whether to revert to the stock script.
5. Do not attempt to enable additional FSM languages in production. The infrastructure is in place but translation files are not shipped — contact your NetSuite Account Manager if you need to participate in translation testing.

Caveats

Oracle's notes do not name the specific scheduled script internal ID, the Employee record field internal ID for the Field Service password, or the script governance impact of the contact-attachment fix. If you depend on any of these in custom code, verify field IDs and script IDs directly in your account before assuming behavior parity.