FSM SuiteApp 2025 Releases: New Bundle ID, Idempotency Keys, HTML Sanitization, and Internationalization

Bundle ID Change (2025.07.x)

This is the most disruptive change in the 2025 cycle. Starting with version 2025.07.x, the FSM SuiteApp bundle ID changed:

• Old bundle ID: 138180
• New bundle ID: 570821

The SuiteApp remains a managed bundle, but any scripts, integrations, saved searches, or configuration files that reference the old bundle ID will break. In particular, service report XML paths in your active config file are automatically updated on upgrade — but inactive config files are not. If you switch to an inactive config, you must manually verify that XML paths no longer reference 138180. See SuiteAnswers ID 1021147 for details.

Mobile Sync Idempotency Keys (2025.10.3)

The FSM mobile sync process now generates a unique idempotency key on each draft record before syncing. This prevents duplicate record creation during repeated sync attempts. A 3-second debounce was also added to the resync trigger when the device comes back online.

Custom tab impact: The idempotency feature works automatically for standard mobile tabs. For custom tabs, you must create an idempotency field on the target record and reference it in your mobile configuration. See Oracle's documentation on Idempotency in Field Service Management for the field setup.

HTML Sanitization in Mobile Configuration (2025.10.3)

Embedded HTML content in configuration (e.g., Task details rendered in the mobile app) is now sanitized before rendering. Some HTML tags that previously rendered will no longer work. Oracle published an allowlist of supported tags and attributes:

• Supported tags: Standard document structure (<div>, <section>, <header>, etc.), text formatting (<p>, <span>, <strong>, <em>, etc.), graphics (<img>, <svg>, <g>, <path>), forms (<form>, <input>, <button>, <select>), and embeds (<iframe>).
• Supported attributes: id, class, style, href, target, src, alt, onclick, onchange, type, value, and others. Notably, <style> and <script> tags are listed as supported, which is unusual for a sanitization pass — verify behavior in your environment.

If you have custom HTML in your FSM configuration that uses tags outside this allowlist, it will stop rendering after the 2025.10.3 upgrade.

Internationalization / Localization (2025.10.3)

FSM now respects the user's browser locale for dates, times, and number formatting across the schedule board, mobile app, and NetSuite UI. Language translations (including scripted strings) are not yet supported — full translation is planned for a future release.

The FSM translation collection custcollection_fsm is unlocked for testing. You can:

1. Add translation strings to custcollection_fsm.
2. Create your own translation collection for custom records, fields, and forms.
3. Reference custom translations in configuration.

Text Enhance (AI-Assisted Input) on FSM Records (2025.10.3)

The Text Enhance feature is now available on these specific fields:

• customrecord_nx_repair_notes — Field Service Repair Notes
• customrecord_nx_maintenance_notes — Field Service Maintenance Notes
• customrecord_nx_install_notes — Field Service Install Notes
• customrecord_nx_uninstall_notes — Field Service Uninstall Notes
• custevent_nx_case_details — Field Service Case Details (on Case)
• custevent_nx_internal_note — Field Service Internal Note (on Task)
• custevent_nx_actions_taken — Field Service Actions Taken (on Task)
• custrecord_nx_jobsafety_notes — Safety Check Notes (on Job Safety)

Configuration Preview (2025.07.3)

The Field Service Configuration page now includes a preview field that displays the merged runtime configuration — your custom configuration merged with FSM defaults with all runtime logic applied. This lets you validate configuration before applying changes, which is useful for debugging configuration inheritance issues.

Subsidiary Field Removed from Configuration (2025.07.3)

The subsidiary field has been removed from the Field Service Configuration page. Oracle states this does not affect subsidiary-related functionality — creating, viewing, and editing config files works as before.

Time Tracking Association Change (2025.04.4)

Time bill records created for completed tasks are now associated with the Task record instead of the Case record. Previously, time bills could be deleted if the associated Case was updated immediately after the time entry was created, due to simultaneous background script execution. If you have saved searches, workflows, or scripts that query time records by Case association, update them to query by Task association instead.

24.2 Permission Model Support (2025.01.1)

FSM now supports the new access levels that replaced the No Permission Required access type for custom records, introduced in NetSuite 24.2. If you previously relied on the old permission model for FSM custom records, verify your role configurations after upgrading.

Mobile App Behavior Notes

• Forced logout on 2025.10.4: The table rendering performance fix forces a mobile app logout. Users must restart and log in again. Administrators should notify users to save work before the update window.
• Geolocation in file uploads (2025.10.5): Files uploaded via File block, Image block, or Files tab now include timestamp and geolocation coordinates in the file description in the File Cabinet.
• Mobile user limit fix (2025.01.1): A login issue affecting accounts with more than 1,000 mobile users was resolved.

What to Do

1. Update bundle references immediately. Search your scripts, saved searches, workflows, and any integration code for bundle ID 138180 and replace with 570821. Check inactive FSM config files for old XML paths referencing the old bundle.
2. Audit custom HTML in FSM configuration. Compare your embedded HTML against the published allowlist. Any unsupported tags will silently stop rendering after 2025.10.3.
3. Add idempotency fields to custom mobile tabs. If you have custom tabs in FSM Mobile, create an idempotency field on the target record and reference it in your tab configuration to prevent duplicate record creation.
4. Update time record queries. If you have saved searches, workflows, or SuiteScript that find time bill records via Case association, update them to look up by Task association instead (per the 2025.04.4 change).
5. Review custom record permissions. After upgrading from pre-24.2, verify that roles accessing FSM custom records have the correct new-model access levels configured.
6. Test locale formatting. Verify that date, time, and number formatting in the schedule board and mobile app renders correctly for your user base's browser locales.
7. Communicate the 2025.10.4 forced logout. Notify mobile field technicians before deploying this version — the app will force a logout and require a restart.