FSM Configuration Record

The Field Service Configuration record stores account-specific Field Service Management (FSM) settings as JavaScript Object Notation (JSON). FSM combines active custom configuration with its standard product defaults to determine supported behavior in NetSuite, the Schedule Board, and FSM Mobile.

Each record holds a configuration revision. An inactive revision can remain available for reference without contributing its JSON to the configuration FSM loads. The stored JSON is the account's custom configuration. It is not a complete copy of the standard product configuration or a saved copy of Configuration Preview.

Record Information

Use these identifiers to distinguish the record and its stored data from labels and temporary controls on the form.

Property	Value
Record type	FSM custom record
Record name	Field Service Configuration
Record ID	`customrecord_nx_configuration`
Record identity	NetSuite Internal ID (`internalid`)
Revision name	Name (`name`)
Stored custom configuration	JSON (`custrecord_nx_json`)

Property

Value

Record type

FSM custom record

Record name

Field Service Configuration

Record ID

customrecord_nx_configuration

Record identity

NetSuite Internal ID (internalid)

Revision name

Name (name)

Stored custom configuration

JSON (custrecord_nx_json)

The FSM record mapping uses id for Internal ID, name for Name, inactive for Inactive and body for the parsed JSON. These are mapping names, not additional NetSuite fields. Use customrecord_nx_configuration as the record type and the stored field IDs when identifying the data in NetSuite searches or scripts.

Forms

On the NetSuite configuration form, the Details group contains Name and Inactive, and the JSON group presents the stored custom configuration.

When Configuration Preview is enabled, create and edit forms label the stored JSON field Editor and add a read-only Preview field. Editor and JSON refer to the same stored field. Preview is a temporary form control and is not saved as a second configuration body. For information about setting up and using Configuration Preview, see Configuration Preview.

This administrative form is separate from the NetSuite forms referenced by FSM Mobile resource configuration. Selecting a form to generate FSM Mobile fields doesn't select or save the configuration record's form. For FSM Mobile form loading, see Form Properties.

Record Relationships

The supplied configuration record has no parent Configuration field or stored references to customer, asset, case, or task records. A configuration can contain record IDs, field IDs, form IDs and other values used by a capability. Those values are settings within JSON, rather than separate relationship fields on the configuration record.

Automatic replacement can retain the previous revision as an inactive record. This doesn't create a stored parent or previous-revision relationship between the two records.

FSM Fields

The following stored fields identify the revision, determine whether FSM loads it and hold its custom settings. Labels can vary by language or account. The field IDs identify the underlying data.

Field	Field ID	Purpose	Important values or behavior
Internal ID	`internalid`	Identifies the saved configuration record.	Separate from the revision's Name. Mapped by FSM as `id`.
Name	`name`	Identifies the configuration revision to administrators.	Manual revisions use an identifiable name. Automatic replacement names begin with Auto Configure. See Updating and Validating FSM Configuration for the naming convention and revision procedure.
Inactive	`isinactive`	Determines whether this revision contributes to loaded custom configuration.	Checked (`T`) excludes the record. Cleared (`F`) makes it active. This is not a script-running, validation or completion indicator.
JSON / Editor	`custrecord_nx_json`	Stores the account-specific custom configuration.	Stored Long Text, required in the supplied record definition, with no declared default. FSM maps its parsed value as `body`. The form label becomes Editor when Preview is enabled.

Field

Field ID

Purpose

Important values or behavior

Internal ID

internalid

Identifies the saved configuration record.

Separate from the revision's Name. Mapped by FSM as id.

Name

name

Identifies the configuration revision to administrators.

Manual revisions use an identifiable name. Automatic replacement names begin with Auto Configure. See Updating and Validating FSM Configuration for the naming convention and revision procedure.

Inactive

isinactive

Determines whether this revision contributes to loaded custom configuration.

Checked (T) excludes the record. Cleared (F) makes it active. This is not a script-running, validation or completion indicator.

JSON / Editor

custrecord_nx_json

Stores the account-specific custom configuration.

Stored Long Text, required in the supplied record definition, with no declared default. FSM maps its parsed value as body. The form label becomes Editor when Preview is enabled.

Form-Only Fields and Indicators

These controls help you interpret the configuration during editing. They don't add stored fields to the record.

Field or indicator	Form control ID	Meaning
Preview	`custpage_config_json_preview`	Displays product defaults combined with the cleaned JSON currently in Editor, including unsaved edits. Preview can appear when you edit an inactive revision. It is read-only and doesn't prove that the displayed changes are saved or active.
JSON validation message	`custpage_config_json_help`	Displays JSON syntax feedback. JSON is valid means the text could be parsed. It doesn't establish supported properties, correct record references or successful processing.

Field or indicator

Form control ID

Meaning

Preview

custpage_config_json_preview

Displays product defaults combined with the cleaned JSON currently in Editor, including unsaved edits. Preview can appear when you edit an inactive revision. It is read-only and doesn't prove that the displayed changes are saved or active.

JSON validation message

custpage_config_json_help

Displays JSON syntax feedback. JSON is valid means the text could be parsed. It doesn't establish supported properties, correct record references or successful processing.

The record has no supplied field recording that configuration maintenance is running or complete, and no supplied Field Service Error reference field. Script execution and the resulting configuration changes are separate facts.

Creation and Update Sources

Configuration revisions can be created or changed manually and by FSM maintenance. Automatic changes occur only when the applicable maintenance identifies a change to make.

Source	Effect on the record
NetSuite configuration entry and Save As	Creates or edits custom JSON and revision details. Save As can create a separate revision and preserve the earlier record. Activation is managed through Inactive.
Automatic configuration maintenance	Can replace the active revision to update identified FSM Mobile endpoint links or apply a bundled account update when the current value matches the expected value.
Form expression maintenance	Can replace the active revision when migrating identified expressions from earlier versions in its JSON.
Account maintenance	Can replace the active revision when migrating the Time Tracking selection from an earlier version into configuration.
Notification maintenance	Can replace the active revision when removing identified deprecated bundle paths.

Source

Effect on the record

NetSuite configuration entry and Save As

Creates or edits custom JSON and revision details. Save As can create a separate revision and preserve the earlier record. Activation is managed through Inactive.

Automatic configuration maintenance

Can replace the active revision to update identified FSM Mobile endpoint links or apply a bundled account update when the current value matches the expected value.

Form expression maintenance

Can replace the active revision when migrating identified expressions from earlier versions in its JSON.

Account maintenance

Can replace the active revision when migrating the Time Tracking selection from an earlier version into configuration.

Notification maintenance

Can replace the active revision when removing identified deprecated bundle paths.

When automatic maintenance changes the JSON, FSM creates an Auto Configure revision and inactivates the previous active revision. If no JSON change is needed, FSM doesn't create a revision. The previous record's JSON remains available for reference.

FSM's Configuration user event also requests script-deployment maintenance after submission. This is a request for background work, not a stored execution status on the configuration record. For script identities, monitoring and operational controls, see FSM Script Reference. For supported manual changes and activation, see Updating and Validating FSM Configuration.

Used by FSM Features

The record supplies custom settings shared across FSM capabilities. Feature topics explain how these settings affect each feature's behavior. The corresponding configuration topics define supported choices and dependencies. The record itself doesn't establish that every property it contains is supported or applied.

Use FSM Configuration to find the relevant configuration area. For record-model settings, NetSuite view settings, and FSM Mobile resource settings, see Related topics.

Record Constraints and Data Requirements

Keep one configuration record active. FSM can load and combine JSON from multiple active records. Automatic replacement uses the first active record returned. Multiple active revisions can therefore produce an unexpected combined configuration. Follow How Configuration Works for the supported active-revision arrangement.

The JSON field is required in the supplied record definition. Custom configuration is a JSON object. FSM's supplied save handler rejects text that cannot be parsed as JSON when you create or edit a record. It also removes formatting whitespace from stored object content. Formatting shown in Editor can differ from the stored text. A syntax check doesn't comprehensively validate configuration paths, property values, searches, expressions or account setup. See Validating the Draft.

Access is controlled by the custom record's permissions. The supplied definition grants the Full permission level to the Administrator, Field Service Administrator, and Field Service System roles. Form visibility and an editable text area don't establish permission to make every configuration change.