FSM Installation Record

A Field Service Management (FSM) installation record stores installation results and supporting details. It can identify the asset being installed, the related project, case, or task, and the employee recorded as completing the work. It also stores the installation outcome, notes, and image.

FSM supplies this custom record as Field Service Install. The installation record holds service evidence separately from the asset's equipment information and the task's schedule, assignment, and status.

Record Information

The following table lists the record's identifiers and supplied entry form.

Property	Value
Record type	FSM custom record
Supplied record name	Field Service Install
Record type ID	`customrecord_nx_install`
Record identity	NetSuite Internal ID (`internalid`)
Supplied FSM entry form	Field Service Install (`custform_nx_install`)

Property

Value

Record type

FSM custom record

Supplied record name

Field Service Install

Record type ID

customrecord_nx_install

Record identity

NetSuite Internal ID (internalid)

Supplied FSM entry form

Field Service Install (custform_nx_install)

Use customrecord_nx_install to identify the record type in FSM article and search definitions. Field labels can vary by account and form.

Forms

The supplied Field Service Install form (custform_nx_install) groups the linked records and service details. It is marked preferred and has Store Form with Record enabled. When you view or edit a record, NetSuite uses the form stored with that record instead of the preferred form. Account-created forms can provide a different layout. For information about form selection and storage in NetSuite, see Custom Entry Form Properties.

The ten supplied custom fields are optional in both the record definition and the supplied form. Neither the record definition nor the supplied form sets initial values for Asset, Project, Case, Task, Project Task, Completed By, or Outcome. Initial values and additional requirements can depend on the entry context, account forms, sourcing, or FSM Mobile configuration.

A configured FSM Mobile resource can use a NetSuite form to generate fields. The resource's mappings, initial values, and field overrides determine how those fields appear in FSM Mobile. A tab label in FSM Mobile doesn't identify the underlying record type or field mappings. Form generation is separate from the form stored with a saved installation record. For information about form loading and article relationships, see FSM Mobile Resource Properties Reference.

Record Relationships

The installation record stores each of the following references. Each reference selects one related record. Several installation records can reference the same asset or work record.

Related Record	Relationship and Field ID	Purpose
Asset	Installation Asset (`custrecord_nx_install_asset`) references Field Service Asset (`customrecord_nx_asset`).	Identifies the equipment or service location associated with the installation result.
Project	Installation Project (`custrecord_nx_install_project`) references project (`job`).	Associates the result with the wider service project.
Case	Installation Case (`custrecord_nx_install_case`) references case (`supportcase`).	Associates the result with a service request or occurrence.
CRM Task	Installation Task (`custrecord_nx_install_task`) references task (`task`).	Associates the result with an individual service visit.
Project Task	Installation Project Task (`custrecord_nx_install_project_task`) references project task (`projecttask`).	Provides a separate link for project-based work. It is distinct from the CRM Task field.
Employee	Installation Completed By (`custrecord_nx_install_completed_by`) references employee (`employee`).	Identifies the employee recorded against the installation result. It is separate from the task's assignee and team.

Related Record

Relationship and Field ID

Purpose

Asset

Installation Asset (custrecord_nx_install_asset) references Field Service Asset (customrecord_nx_asset).

Identifies the equipment or service location associated with the installation result.

Project

Installation Project (custrecord_nx_install_project) references project (job).

Associates the result with the wider service project.

Case

Installation Case (custrecord_nx_install_case) references case (supportcase).

Associates the result with a service request or occurrence.

CRM Task

Installation Task (custrecord_nx_install_task) references task (task).

Associates the result with an individual service visit.

Project Task

Installation Project Task (custrecord_nx_install_project_task) references project task (projecttask).

Provides a separate link for project-based work. It is distinct from the CRM Task field.

Employee

Installation Completed By (custrecord_nx_install_completed_by) references employee (employee).

Identifies the employee recorded against the installation result. It is separate from the task's assignee and team.

The Asset, Project, Case, CRM Task, and Project Task fields are supplied parent-record links. They enable NetSuite parent/child record relationships and related sublists. They don't create an equipment hierarchy or add FSM asset inheritance to the installation record. Completed By is an employee reference, not a parent-record link.

The supplied Asset, Case, Project, and CRM Task forms contain related installation sublists. Their availability depends on the form used and record access. The relationship is held on the installation record, rather than in a single installation field on the parent.

An installation record has no supplied item, quantity, or units field. The linked asset can identify an item through Asset Item (custrecord_nx_asset_item). The Asset Item relationship is stored on the asset. Item usage, inventory quantities, and fulfillment remain separate data. See FSM Asset Record and FSM Asset Processing from Item Fulfillments.

Account custom links don't automatically add records to FSM Mobile, service history, reports, inheritance, or synchronization. Each capability uses its own configured relationships and selection.

FSM Fields

The preceding table lists relationship fields. The following table lists the remaining custom fields and the standard External ID field.

Field	Field ID	Purpose	Values and Behavior
Outcome	`custrecord_nx_install_outcome`	Records the installation result.	Selects from Field Service Complete (`customlist_nx_complete_incomplete`): Complete, Incomplete, or N/A. No selection is supplied as a record default.
Notes	`custrecord_nx_install_notes`	Stores installation service notes.	Text Area. Separate from native User Notes on the record.
Image	`custrecord_nx_install_image`	Stores a supporting installation image reference.	Image field. Separate from the record's general file attachments.
Idempotency Key	`custrecord_nx_install_idem_key`	Retains the older custom creation-identity field.	Kept for compatibility and visibility. Standard FSM Mobile creation uses native External ID instead.
External ID (standard)	`externalid`	Stores the FSM Mobile creation key when the resource uses standard FSM record synchronization.	FSM stores the key with the `fsm_` prefix. The key identifies record creation rather than the installation outcome.

Field

Field ID

Purpose

Values and Behavior

Outcome

custrecord_nx_install_outcome

Records the installation result.

Selects from Field Service Complete (customlist_nx_complete_incomplete): Complete, Incomplete, or N/A. No selection is supplied as a record default.

Notes

custrecord_nx_install_notes

Stores installation service notes.

Text Area. Separate from native User Notes on the record.

Image

custrecord_nx_install_image

Stores a supporting installation image reference.

Image field. Separate from the record's general file attachments.

Idempotency Key

custrecord_nx_install_idem_key

Retains the older custom creation-identity field.

Kept for compatibility and visibility. Standard FSM Mobile creation uses native External ID instead.

External ID (standard)

externalid

Stores the FSM Mobile creation key when the resource uses standard FSM record synchronization.

FSM stores the key with the fsm_ prefix. The key identifies record creation rather than the installation outcome.

Outcome records the installation result independently of the linked task's status. An outcome doesn't confirm task completion, inventory fulfillment, or asset creation. The supplied installation fields don't include a processing request, running status, completion timestamp, or dedicated error reference.

For the creation-identity mechanism and its scope, see FSM Mobile Duplicate Creation Protection.

Creation and Update Sources

The following table describes how installation records can be created or updated.

Source	Record Effect
NetSuite entry	Creates or edits installation data through an available form, subject to record permissions and applicable validation.
Configured FSM Mobile resource	Can create or update mapped installation data when the account supplies an article definition for `customrecord_nx_install` and permits the operation. The definition controls which work record is linked and which fields are saved.
Standard FSM Mobile synchronization	Maintains External ID for creation identity and can recognize an earlier creation using the same key. This applies when the configured resource uses the standard synchronization path.

Source

Record Effect

NetSuite entry

Creates or edits installation data through an available form, subject to record permissions and applicable validation.

Configured FSM Mobile resource

Can create or update mapped installation data when the account supplies an article definition for customrecord_nx_install and permits the operation. The definition controls which work record is linked and which fields are saved.

Standard FSM Mobile synchronization

Maintains External ID for creation identity and can recognize an earlier creation using the same key. This applies when the configured resource uses the standard synchronization path.

The presence of this record type doesn't make an Installation tab available on every task in FSM Mobile. FSM Mobile form generation, local entry, and successful NetSuite synchronization are separate stages. The supplied record definition doesn't set Completed By to the current technician.

Used by FSM Features

The following table describes how FSM features use installation records.

Feature	Record Use
FSM Mobile Duplicate Creation Protection	Protects eligible creation requests when an installation resource uses standard record synchronization.
FSM Service Reports and Notifications	Can present saved installation results when the selected report data and template include them. A relationship alone doesn't add the result to a report.

Feature

Record Use

FSM Mobile Duplicate Creation Protection

Protects eligible creation requests when an installation resource uses standard record synchronization.

FSM Service Reports and Notifications

Can present saved installation results when the selected report data and template include them. A relationship alone doesn't add the result to a report.

For information about record selection and report layout, see FSM Service Report Configuration.

Record Constraints and Data Requirements

The supplied definition doesn't require any of its ten custom fields. A particular form or FSM Mobile resource can require additional values. FSM Mobile entry counts and completion validation depend on the resource configuration. The record definition doesn't enforce one installation record per task or asset.

The work references are stored in separate fields. Selecting a CRM task alone doesn't confirm that its asset, case, and project references are saved on the installation record. Initial values and synchronization between these relationships depend on the entry method and configuration.

The record is not hierarchical. Its parent-record links don't make another installation record its parent. Linking the record to an asset also doesn't create or update that asset through fulfillment processing.