FSM Configuration Preview: Inspect Merged Runtime Config in Field Service

NetSuite's Field Service Management (FSM) module now includes a Configuration Preview capability that lets admins view the final merged runtime configuration — the combination of the core FSM product config and any custom config entries — directly on the Configuration record.

What changed

When enabled, the Field Service Configuration record (Field Service > Administration > Configuration) gains a second read-only JSON field called Preview alongside the existing Editor field. The Preview field renders the result of merging your custom JSON with the core product config that FSM ships for your account (which varies depending on enabled NetSuite features).

Merge behavior

• Custom properties that overlap with core config override the core value (string, number, or Boolean — all override).
• Non-overlapping custom properties are added to the core config.
• Property name matching is case-insensitive.
• Properties set to null are not merged (effectively a no-op/removal).
• JavaScript-style comments (//) in custom config are stripped during merge.
• Validation runs on save; only the first error is surfaced.

How to enable

1. Navigate to Field Service > Administration > Configuration.
2. In the JSON Editor field, add or merge the following property into your existing custom config:
   {"config": {"preview": true}}
3. Click Save. The record will reload in edit mode showing both Editor and Preview fields.

What to do

• Admins troubleshooting FSM behavior: Enable the preview to confirm which config values are actually active at runtime, rather than guessing what the core product ships.
• Developers building FSM customizations: Use the preview to validate that your overrides land correctly and that case-insensitive matching isn't causing unexpected collisions.
• Note: The source documentation does not specify which NetSuite release introduced this feature. Verify availability in your account's release version and confirm the feature is present on your Configuration record before relying on it in production.