FSM SuiteApp Gets New Bundle ID and Configuration Preview in 2025.07.3

What changed

New Bundle ID

Starting with version 2025.07.x, the FSM SuiteApp ships under bundle ID 570821, replacing the old bundle ID 138180. The SuiteApp remains a managed bundle, so updates still flow through SuiteBundler. Any scripts, workflows, or integrations that reference the old bundle ID by number — for example, nlapiLoadRecord calls that check bundle metadata, or deployment scripts that validate installed bundles — must be updated.

Configuration Preview

The Field Service Configuration page now includes a preview field that renders the merged runtime configuration in real time. This merges your custom configuration with FSM defaults and applies all runtime logic, letting you validate settings before they take effect. This is a read-only preview; no new API or record-level changes are involved.

Subsidiary Field Removed from Configuration Page

The subsidiary field has been removed from the Field Service Configuration page UI. Oracle states this does not affect subsidiary-related functionality — config file CRUD operations work as before. However, if you have custom scripts or saved searches that target this field on the configuration record, verify they still function correctly.

Issue Fixes

• Child Asset Tabs (FSM Mobile) — Tabs no longer collapse on state changes such as geolocation updates.
• Task Service Report Images — PDF attachments from mobile task completion now render images correctly.
• Case Records Linked to Sales Orders — Cases linked to Sales Orders with a payment method no longer throw an invalid record transformation error on load.
• Status Update Queue Processing — An error updating the Field Service Update Status checkbox on one record no longer blocks processing of subsequent records in the queue.
• Asset Address Search — Results now prioritize locations near the user and display in a logical order.
• Service Report Generation — Outdated bundle ID references in service report XML paths have been removed. On upgrade, the system auto-updates paths in the active config file only.

What to do

1. Check inactive config files for old bundle ID references. After upgrading to 2025.07.3, the system updates XML paths in your active config file automatically. If you switch to an inactive config file, manually verify that XML paths do not reference the old bundle ID (138180). Replace any occurrences with 570821. See SuiteAnswers ID 1021147 for detailed instructions.
2. Search your codebase for the old bundle ID. Run a search across SuiteScripts, workflows, and any external integrations for references to 138180. Update them to 570821.
3. Validate subsidiary-related customizations. If you had scripts or saved searches referencing the subsidiary field on the FSM configuration record, confirm they still work after the field's removal from the UI.
4. Test service reports end-to-end. After upgrading, generate a service report from the mobile app and confirm images render in the PDF attachment and the report delivers successfully.
5. Review the new configuration preview. Use the preview field on the Field Service Configuration page to verify that your custom settings merge correctly with FSM defaults before activating changes.