FSM Uninstallation Record

A Field Service Management (FSM) uninstallation record captures the result and supporting details of uninstallation work on an asset. It can connect that result to a project, case, customer relationship management (CRM) task, or project task. It can also identify the employee recorded as completing the work.

FSM supplies this custom NetSuite record as Field Service Uninstall. It stores service evidence separately from the asset's equipment details and the task's schedule and status.

Record Information

Use the record and field IDs when working with searches, mappings, and integrations. Labels can vary by account or language.

Property

Value

Record type

FSM custom record

Supplied record name

Field Service Uninstall

Record ID

customrecord_nx_uninstall

Record identity

NetSuite Internal ID (internalid)

Supplied NetSuite form

Field Service Uninstall (custform_nx_uninstall)

This topic uses uninstallation to refer to the record supplied with the Uninstall label and the technical suffix uninstall. These names identify the same record and don't refer to a separate NetSuite transaction type.

Forms

The supplied Field Service Uninstall entry form places the relationship fields in the Related Records group. The Service Details group contains Outcome, Completed By, Notes, and Image. All ten custom fields are optional in both the supplied record definition and this form.

The supplied form is marked Preferred and has Store Form with Record enabled. NetSuite retains the form used to create each record and uses that form when you view or edit the record. Account-created forms can present the same data differently and impose additional requirements. For standard form selection and storage behavior, see Custom Entry Form Properties.

If an account configures this record as an FSM Mobile resource, a NetSuite form can supply the fields generated for FSM Mobile. That form-loading choice is separate from the NetSuite UI form stored with the saved record. For information about field overrides, initial values, and validation for FSM Mobile, see Form Properties.

Record Relationships

Each relationship in the following table is an FSM-supplied field stored on the uninstallation record. Each field selects one related record. Several uninstallation records can reference the same related record.

Related record

Relationship and field ID

Purpose

Asset

Asset (custrecord_nx_uninstall_asset) references customrecord_nx_asset.

Identifies the equipment or service site associated with the result.

Project

Project (custrecord_nx_uninstall_project) references a NetSuite project (job).

Connects the result to the wider service context.

Case

Case (custrecord_nx_uninstall_case) references supportcase.

Connects the result to the service request or occurrence.

CRM Task

Task (custrecord_nx_uninstall_task) references task.

Connects the result to an individual CRM service visit.

Project Task

Project Task (custrecord_nx_uninstall_project_task) references projecttask.

Provides a separate link for work performed through project tasks.

Employee

Completed By (custrecord_nx_uninstall_completed_by) references employee.

Identifies the employee recorded as completing the work. This field is separate from task assignment and the record's native Owner.

The Asset, Project, Case, Task, and Project Task fields are defined as parent-record links in NetSuite. The supplied Asset, Project, Case, and CRM Task forms include related Uninstall sublists. These links support related-record presentation; they don't form an asset equipment hierarchy or define FSM inheritance.

The record has no supplied direct Item field. The linked asset can identify an item through Asset Item (custrecord_nx_asset_item), stored on the asset. This is an indirect relationship, rather than an item value captured on the uninstallation record. See Record Relationships.

The CRM task and project task links are distinct. Linking a CRM task to a project doesn't make it a project task. A custom relationship added by an account doesn't automatically add data to FSM Mobile, history, reports, or synchronization.

FSM Fields

The six relationship fields are described in Record Relationships. The following fields capture the result and its supporting information or identify a synchronized entry.

Field

Field ID

Purpose

Important values or behavior

Outcome

custrecord_nx_uninstall_outcome

Records the selected uninstallation result.

Uses customlist_nx_complete_incomplete, whose supplied choices are Complete, Incomplete, and N/A. This is service-result data, separate from the linked task's Status.

Notes

custrecord_nx_uninstall_notes

Stores written details about the work or result.

A text area with NetSuite Text Enhance enabled where available. The field is separate from native User Notes and System Notes.

Image

custrecord_nx_uninstall_image

Stores a supporting image reference.

A single Image field, separate from files attached through the record's Files subtab.

Idempotency Key

custrecord_nx_uninstall_idem_key

Retains the older custom creation-identity value.

Compatibility field. Current standard FSM Mobile record creation uses native External ID instead.

External ID (standard)

externalid

Holds the creation identity used by standard FSM Mobile synchronization when this record uses that path.

FSM uses the fsm_ prefix. It is separate from Internal ID, Outcome, and the older custom Idempotency Key.

Selecting Complete records an outcome. It doesn't establish that the linked task is Completed, that a script ran, or that stock was returned. The supplied record has no dedicated processing-request, running, completion-timestamp, or Field Service Error reference field.

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

Creation and Update Sources

The method and configuration used to create or edit the record determine which data is supplied. The record definition doesn't supply initial values or sourcing rules for its ten custom fields.

Source

Effect on the record

NetSuite entry

Creates or edits the custom record through an available form, subject to record and field permissions. Related sublists provide its service-work context.

Account-configured FSM Mobile resource

Can read and synchronize mapped record data when the account includes this record in its resource configuration. Its form, mappings, defaults, and validation determine the fields used.

The supplied record type doesn't itself create an FSM Mobile tab or require an uninstallation entry for every task. Resource properties and field loading are described in FSM Mobile Resource Properties Reference. Saved-field mappings are described in FSM Searches and Field Mapping.

Used by FSM Features

These capabilities can use the record when the relevant account configuration includes it.

Feature

How the record is used

FSM Mobile Duplicate Creation Protection

Protects repeated creation requests when the configured resource uses standard record synchronization.

FSM Service Reports and Notifications

Can include saved uninstallation data when the report definition supplies it and the selected template displays it. A relationship alone doesn't include it in a report.

Uninstallation result capture is separate from stock transfer processing. For the Return tab and its transaction results, see FSM Mobile Stock Transfers.

Record Constraints and Data Requirements

The supplied record definition stores all ten custom fields, marks none as required, and supplies no default selections or values. A form, FSM Mobile resource, or account customization can impose additional requirements. An optional record field doesn't establish that an entry is complete or usable for a particular service process.

The separate Project, Case, Task, and Project Task fields don't by themselves guarantee that all selected records belong to the same service work. When entering or mapping data, verify that the selected records belong to the intended service work.

The record documents an uninstallation result. Saving it doesn't by itself establish an inventory return, an asset deletion, or a change to the asset's service location. Those outcomes require their own applicable operations.

Additional Information

Related Topics

General Notices