FSM Repair Record
The Field Service Management (FSM) repair record stores details and results of repair work. These details include the related asset, service work, employee, outcome, notes, and image. It is an FSM custom record in NetSuite, displayed as Field Service Repair.
A repair record is separate from the asset being serviced and the case or task that organizes the work. Selecting Repair as a Case Type doesn't itself create a repair record.
Record Information
Use the record type and field IDs when working with searches, mappings, or integrations. Account labels can differ from the supplied English labels.
|
Property |
Value |
|---|---|
|
Record type |
FSM custom record |
|
Record name |
Field Service Repair |
|
Record type ID |
|
|
SuiteScript record and search type |
|
|
Saved record identity |
NetSuite Internal ID ( |
|
Supplied entry form |
Field Service Repair ( |
An FSM Mobile resource ID, such as repairrecord in an account configuration, identifies a resource definition. It is separate from the NetSuite record type and the internal ID of an individual repair.
Forms
FSM supplies the Field Service Repair custom entry form (custform_nx_repair). The supplied definition sets this as the preferred form and enables Store Form with Record. NetSuite uses the form stored with a repair record to view or edit that record, regardless of the preferred form. For more information, see Custom Entry Form Properties.
The form groups the related-record links separately from Completed By, Outcome, Notes, and Image. All ten supplied repair custom fields are optional on this form. Account-created forms can change field presentation and requirements.
When an account configures an FSM Mobile resource to load a NetSuite form for repair, that form supplies generated FSM Mobile field definitions. Generating FSM Mobile fields is separate from retaining a form with the saved repair record. The resource's field overrides, mappings, and defaults determine which fields FSM Mobile displays and which values it saves. For more information, see Form Properties.
Record Relationships
The following table lists the relationships stored on a repair record. Each field holds one reference, and multiple repair records can reference the same related record.
|
Related record |
Relationship and field ID on Repair |
Purpose |
|---|---|---|
|
Asset |
Asset ( |
Identifies the equipment or service location associated with the repair. |
|
Project |
Project ( |
Associates the repair with a project. |
|
Case |
Case ( |
Associates the repair with a service request. |
|
CRM Task |
Task ( |
Associates the repair with an individual service visit. |
|
Project Task |
Project Task ( |
Associates the repair with project-based work. This is a separate field and record type from CRM Task. |
|
Employee |
Completed By ( |
Identifies the employee recorded against the repair result. It is separate from the task's assignee or resource assignments. |
The Asset, Project, Case, Task, and Project Task fields are supplied FSM links defined as NetSuite parent-record relationships. Related repair records can appear in parent sublists when the form includes those sublists. Completed By is an employee reference, not a parent-sublist relationship.
These links don't form an asset hierarchy or automatically inherit the asset's fields. A link added by an account customization doesn't automatically include the record in FSM Mobile, history, reports, or synchronization. See Assets and Service Records for the distinction between assets and related service records.
FSM Fields
The supplied repair custom fields store their values on the repair record. Relationship fields are included here for a complete field reference.
|
Field |
Field ID |
Purpose |
Important values or behavior |
|---|---|---|---|
|
Asset |
|
Asset associated with the repair. |
Single Field Service Asset reference. |
|
Project |
|
Project associated with the repair. |
Separate from the Case and task links. |
|
Case |
|
Service request associated with the repair. |
Single Case reference. |
|
Task |
|
CRM service visit associated with the repair. |
References |
|
Project Task |
|
Project Task associated with the repair. |
Separate from Task. |
|
Completed By |
|
Employee recorded against the repair result. |
Doesn't establish the task's assignment or completion status. |
|
Outcome |
|
Recorded repair result. |
Options from Field Service Complete ( |
|
Notes |
|
Repair details entered as text. |
Text Area field that is separate from Task Actions Taken and NetSuite User Notes. |
|
Image |
|
Image associated with the repair. |
One Image field that is separate from the record's general Files attachments. |
|
Idempotency Key |
|
Earlier custom field for identifying creation requests, retained for compatibility. |
Current standard FSM Mobile record synchronization uses native External ID instead. This field is not a repair-completion or script-running indicator. |
The following native fields have particular relevance to configured FSM Mobile creation and form selection.
|
Field |
Field ID |
Meaning in FSM |
|---|---|---|
|
External ID |
|
Standard FSM Mobile record synchronization stores creation identity with the |
|
Custom Form |
|
Identifies the NetSuite entry form selected for the record. FSM Mobile form generation has its own resource configuration. |
For creation-identity behavior and its scope, see FSM Mobile Duplicate Creation Protection.
The Outcome field describes the repair result without changing or confirming the linked task's Completed status. Date Created and Last Modified are record audit dates, not dedicated repair start or completion timestamps. The supplied repair field set has no processing-request flag, running-status field, or direct Field Service Error link.
Creation and Update Sources
The following table describes how each source affects repair data.
|
Source |
Effect on the record |
|---|---|
|
NetSuite entry |
Creates or edits repair data through the available entry form, subject to record permissions and account requirements. |
|
Configured FSM Mobile resource |
Reads, creates, or updates the fields specified by its article definition and mappings when those operations are enabled. A successful synchronization saves the repair record in NetSuite, so local entry alone doesn't confirm that the record was saved. |
|
Form and resource defaults |
Can supply initial values for a configured creation path. A resource's configured parent field can supply the current event relationship, but other links and Completed By require separate value sources. |
The record type alone doesn't add a Repair tab to every task. Saving an asset, case, or task doesn't automatically create a repair record. Resource selection, forms, field mappings, and permitted operations are defined in FSM Mobile Resource Selection and Shared Data and FSM Mobile Resource Properties Reference.
Used by FSM Features
The following table shows how FSM features and configured resources use repair records.
|
Feature or configured use |
How the record is used |
|---|---|
|
FSM Mobile repair capture |
An account-configured resource can capture repair details against the configured service context. The resource definition determines the fields and relationships used. |
|
Applies to repair creation requests that use standard record synchronization and retain FSM creation identity. |
|
|
Repair data can be included when both the report's data definition and selected template include that data. A related-record link alone doesn't add repair data to a report. |
For report data and template dependencies, see Supplying Data to FSM Service Report Templates.
Record Constraints and Data Requirements
The supplied record definition doesn't require any of the ten repair custom fields or provide an initial selection for Outcome or Completed By. An account form or FSM Mobile resource can impose requirements and initial values for a particular entry path. Those settings apply only to that entry path.
The relationships are independent stored references. Setting Task doesn't automatically set Project Task, Case, Project, Asset, or Completed By. The supplied definition doesn't impose one repair per task or asset.
The supplied Asset field prevents ordinary deletion of an asset that a repair record still references. The Project, Case, Task, Project Task, and Completed By fields allow deletion of the referenced record and clear the corresponding repair field. These field settings don't request deletion of the repair itself. Other dependencies and account rules can also prevent deletion. See Customizing Delete Behavior for Records Referenced by Custom Fields.