FSM Maintenance Record
A Field Service Management (FSM) maintenance record captures information about maintenance work performed on an asset. It stores the service result, notes, and supporting image separately from the asset's descriptive information and the task that represents the visit.
FSM supplies this custom NetSuite record with links to an asset, project, case, customer relationship management (CRM) task, and project task. Another link identifies the employee recorded as completing the maintenance. Account-specific fields can capture additional checklist results or measurements.
Record Information
Field labels can vary by account or form. Use the record and field IDs to identify the underlying data.
The following table identifies the maintenance record and supplied form.
|
Property |
Value |
|---|---|
|
Record type |
FSM custom record |
|
Record name |
Field Service Maintenance |
|
Record ID |
|
|
Record identity |
NetSuite Internal ID ( |
|
Supplied FSM form |
Field Service Maintenance ( |
Use customrecord_nx_maintenance as the record type for NetSuite record operations and searches. An FSM Mobile resource name such as maintenance is a configuration identifier, rather than a different NetSuite record type.
Forms
The supplied Field Service Maintenance entry form (custform_nx_maintenance) groups related records and service details. The supplied form is preferred, with the Store Form with Record box checked. NetSuite stores the form used to enter a record and uses that form when the record is viewed or edited. Account form and role settings can affect which form is available when you create a record. For more information, see Custom Entry Form Properties.
You can create additional maintenance forms for your account's service processes. The fields, labels, and requirements on these custom forms can differ from the supplied form.
When an account configures a maintenance resource in FSM Mobile, a NetSuite form can supply its generated input definitions. The form used to generate inputs is separate from the form stored with the saved maintenance record. Generated fields can include initial values and requirements from the loaded form. Explicit FSM Mobile element configuration can override these definitions. For form loading and overrides, see Form Properties and Form-Generated Properties and Initial Values.
Record Relationships
The following supplied fields are stored on the maintenance record. Each field references one related record, and multiple maintenance records can reference the same asset or record for service work. The asset, project, case, and task links are supplied parent-record relationships that can expose related maintenance records in NetSuite sublists.
|
Related Record |
Relationship and Field ID |
Purpose |
|---|---|---|
|
Maintenance Asset ( |
Identifies the equipment or service location being maintained. |
|
|
Project |
Maintenance Project ( |
Associates the result with wider service work. |
|
Maintenance Case ( |
Associates the result with the service request or occurrence. |
|
|
Maintenance Task ( |
Identifies the service visit associated with the result. |
|
|
Project Task |
Maintenance Project Task ( |
Associates the result with a project task, which is a separate record type from a CRM task. |
|
Employee |
Completed By ( |
Identifies the person recorded as completing the maintenance, independently of task assignment. |
The record stores these links separately. A task link doesn't confirm that the maintenance record's Asset, Case, or Project fields contain values. Creation and synchronization configuration determine which values are supplied.
An additional custom relationship doesn't automatically include a maintenance record in Asset inheritance, FSM Mobile resources, service history, reports, or synchronization. Those uses depend on their own supported configuration and record selection.
FSM Fields
The supplied fields provide service context and a general result. They don't define a fixed checklist for every kind of asset.
Service Context and Results
The following table describes the supplied fields for service context and results.
|
Field |
Field ID |
Purpose |
Values and Behavior |
|---|---|---|---|
|
Asset |
|
Asset being maintained. |
Single asset reference, separate from the asset selected on a linked task. |
|
Project |
|
Wider service-work context. |
Single project reference. |
|
Case |
|
Service request or occurrence. |
Single case reference. |
|
Task |
|
Related CRM task visit. |
Separate from project task. |
|
Project Task |
|
Related project activity. |
Separate from CRM task. |
|
Completed By |
|
Employee recorded as completing the maintenance. |
No employee default is supplied by the field definition. A populated value doesn't establish that the linked task is complete. |
|
Outcome |
|
General maintenance result. |
References Field Service Pass Fail ( |
|
Notes |
|
Details recorded about the maintenance. |
Text Area field, distinct from Task Actions Taken and native User Notes. |
|
Image |
|
Supporting image for the result. |
Image field, separate from other files attached to the record. |
For Outcome mappings, use the account's list-value IDs rather than display labels, which can change or be translated.
Outcome describes the maintenance result. It is not the linked task's native Status, a script execution state, or a synchronization result. Additional checklist questions and measurements depend on the account's custom fields and mappings.
Identity and Record Dates
The following table describes the identity fields and record dates.
|
Field |
Field ID |
Purpose and Values |
|---|---|---|
|
External ID (standard) |
|
Standard FSM Mobile record synchronization stores creation identity here with the |
|
Idempotency Key |
|
Older custom identity field retained for compatibility and visibility. Current standard FSM Mobile record creation uses External ID instead. This is not a maintenance completion indicator. |
|
Date Created (standard) |
|
Records when the maintenance record was created, rather than when the maintenance work was performed. |
|
Last Modified (standard) |
|
Date of the record's latest modification, separate from service completion. |
For the standard creation identity and its synchronization limits, see FSM Mobile Duplicate Creation Protection.
Creation and Update Sources
The following table describes how maintenance records can be created or updated.
|
Source |
Record Changes |
|---|---|
|
NetSuite Maintenance entry |
Creates or edits the custom record and its service relationships using the selected form and the user's permitted access. |
|
Account-configured FSM Mobile resource |
Can create or update mapped maintenance data when the resource is selected for the work and its permissions allow the operation. |
For FSM Mobile resources, the configured parent relationship and defaults determine the supplied context. Saving locally doesn't confirm successful synchronization to NetSuite.
The supplied record doesn't automatically provide a Maintenance tab for every task in FSM Mobile. Use FSM Mobile Resource Properties Reference for resource definitions and FSM Searches and Field Mapping for record selection and save mappings.
Used by FSM Features
The following table describes how FSM features use maintenance records.
|
Feature |
Record Use |
|---|---|
|
Recognizes repeated creation requests when the configured resource uses standard record synchronization. |
|
|
Can present saved maintenance results included in the report data and template. A maintenance link alone doesn't add the result to every service report. |
For including additional saved data in a report, see Adding Data to FSM Service Reports.
Record Constraints and Data Requirements
All ten supplied maintenance custom fields are optional in the record definition and have no supplied selection or text default. The supplied Maintenance form also leaves those custom fields optional. Account forms, FSM Mobile resources, scripts, and other account rules can impose requirements that are specific to the account.
CRM task and project task are separate relationships. Their fields don't establish a rule that both must be populated, or that only one may be populated.
Completed By, Outcome, and the record dates describe different facts. These fields and dates don't confirm task completion, satisfaction of every checklist requirement, or successful synchronization of an entry in FSM Mobile.
A maintenance result doesn't define a recurring service schedule. Future service work is maintained separately from the captured result.