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

Bundle ID Change (2025.07.3+)

Starting with version 2025.07.x, the FSM SuiteApp ships under a new bundle ID:

• Old: 138180
• New: 570821

The SuiteApp remains a managed bundle. Any scripts, integrations, or deployment checks that reference the old bundle ID must be updated. Service report XML paths in the active config file are updated automatically on upgrade, but inactive config files are not patched. If you switch to an inactive config, verify that XML paths do not reference 138180. See SuiteAnswers ID 1021147 for details.

Mobile Sync Idempotency (2025.10.3)

The mobile sync process now generates a unique idempotency key on draft records before syncing. Combined with a 3-second debounce on reconnect resyncs, this prevents duplicate record creation during repeated or interrupted sync attempts.

This works automatically for standard mobile tabs. For custom tabs, you must:

1. Create an idempotency field on the target custom record.
2. Reference that field in the FSM mobile configuration.

See Oracle's documentation on Idempotency in Field Service Management for the configuration schema.

HTML Sanitization in Mobile (2025.10.3)

Embedded HTML content in FSM configuration (e.g., Task details rendered in the mobile app) is now sanitized before rendering. Tags and attributes outside the allowlist will be stripped. Supported tags include structural elements (<div>, <section>, <header>), inline formatting, <img>, <svg> (with d, viewbox, transform, fill), <form>/<input>/<select>, <iframe>, and <style>/<script>. Event attributes like onclick and onchange are allowed. Review any custom HTML blocks in your FSM configuration to ensure they use only supported tags and attributes.

Internationalization / Locale Support (2025.10.3)

FSM now localizes dates, times, and number formats across the schedule board, mobile app, and NetSuite UI based on the user's browser locale. 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, so you can test custom translation strings now. You can also create your own translation collection for custom records, fields, and forms and reference it in FSM configuration.

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

The Text Enhance feature is enabled on these 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 — Case: Field Service Case Details
• custevent_nx_internal_note — Task: Field Service Internal Note
• custevent_nx_actions_taken — Task: Field Service Actions Taken
• custrecord_nx_jobsafety_notes — Job Safety: Safety Check Notes

Configuration Preview (2025.07.3)

The Field Service Configuration page now includes a preview field that merges your custom configuration with FSM defaults and applies all runtime logic. This lets you validate configuration before deploying changes — useful for catching merge conflicts between custom and default settings.

The Subsidiary field was also removed from the Field Service Configuration page in this release, though subsidiary-related functionality is unaffected.

Geolocation in File Uploads (2025.10.5)

Files uploaded from the File block, Image block, or Files tab in the mobile app now include both timestamp and geolocation coordinates in the File Cabinet file description. If you parse file descriptions programmatically (e.g., via SuiteScript or saved searches on the File Cabinet), expect the format to change.

Time Tracking Fix (2025.04.4)

A race condition where time bills for completed tasks were deleted when the associated Case was updated immediately after creation has been fixed. Time records are now associated with the Task record instead of the Case record. If you have saved searches, workflows, or scripts that query time bills via Case relationships, update them to look at the Task association instead.

Custom Record Access Levels (2025.01.1)

FSM 2025.01.1 adds support for the new access levels introduced in NetSuite 24.2 that replace the deprecated No Permission Required access type for custom records. If you have not yet migrated your custom record permissions per Setting Permissions for a Custom Record Type, do so before upgrading.

Mobile App Table Rendering (2025.10.4)

Important: Deploying version 2025.10.4 will log out all mobile users and require an app restart. The update replaces generic HTML cell rendering with layout-system components matched to each cell's data type on resource index pages. Notify mobile users to save work before the update window.

What to Do

1. Update bundle references: Search your scripts, CI/CD pipelines, and deployment tooling for bundle ID 138180 and replace with 570821. Check inactive FSM config files for old XML paths referencing the old bundle.
2. Add idempotency fields for custom tabs: If you use custom mobile tabs, create an idempotency field on the custom record and reference it in FSM configuration to prevent duplicate record creation.
3. Audit embedded HTML: Review any custom HTML blocks in your FSM Task details or mobile configuration. Strip unsupported tags and attributes to avoid content being silently removed by the new sanitizer.
4. Update time-tracking queries: Saved searches, workflows, or SuiteScript that query time bills via Case records should be updated to use the Task record association.
5. Review custom record permissions: Ensure all FSM-related custom records have been migrated from the deprecated No Permission Required access type to the new access levels from NetSuite 24.2.
6. Plan mobile rollout for 2025.10.4: Coordinate the upgrade window since it forces a logout/restart for all mobile users.
7. Test locale formatting: Verify that date, time, and number formatting in the schedule board and mobile app render correctly for your user base's browser locales.