FSM Opportunity Record

An opportunity is a standard NetSuite record for a potential sale to a prospect or customer. Field Service Management (FSM) adds service relationships to preserve the sale's customer, asset, case, and task context.

FSM scripts interact with opportunity records in NetSuite, which remain sales records. For information about sales stages, forecasting, and ordinary opportunity entry, see Opportunity Records.

Note: Standard FSM Mobile doesn't display opportunity records or provide an opportunity workflow. An account can configure a custom FSM Mobile resource for opportunities, but this is outside product support. The customer is responsible for ensuring that the resource functions correctly.

Record Information

Use the record and field IDs to distinguish stored data from account-specific labels.

Property	Value
Record type	Standard NetSuite
Record name	Opportunity
Record ID	`opportunity`
Record identity	NetSuite Internal ID (`internalid`)
FSM record model	`models/opportunity`

Property

Value

Record type

Standard NetSuite

Record name

Opportunity

Record ID

opportunity

Record identity

NetSuite Internal ID (internalid)

FSM record model

models/opportunity

For the native record identifier and scripting reference, see Opportunity.

Forms

FSM supplies opportunity record scripts and service fields. Use an account's standard or customized opportunity form to present those fields. When the FSM form scripts are active, customer and asset selection uses relevant fields that you can see and edit. Changing a label or hiding a field doesn't change its stored field ID.

Opportunity custom transaction forms support Store Form with Record. When enabled, NetSuite retains the form reference with records created using that form. NetSuite displays the stored form when you view or edit the record. When the form is not stored, preferred-form selection applies. This setting is enabled by default for custom transaction forms. See Storing Custom Forms with Transactions.

The default form used when the FSM Opportunity model creates a record is separate from the form displayed when you reopen that record. The standard Opportunity model assigns no custom-form ID. For information about the supported model setting, see Custom Forms for Record Creation. For information about selector controls, see Properties and Defaults.

Record Relationships

The following table lists the opportunity's service references. Each selection field holds one related record, and several opportunities can reference the same service record.

Related Record	Relationship and Field ID	Purpose
Customer or Project	Opportunity native Entity (`entity`) holds the transaction's entity. Without NetSuite Project Management, this can identify a project, whose customer supplies the FSM Customer.	Provides the native sales context.
Customer	Opportunity Field Service Customer (`custbody_nx_customer`) references the customer.	Keeps the customer identifiable separately from a project used as Entity.
Project	With Project Management enabled, opportunity native Project (`job`) holds the project. Without it, the FSM Project mapping writes to `entity`.	Associates the potential sale with a project using the account's native relationship.
Asset	Opportunity Field Service Asset (`custbody_nx_asset`) references Field Service Asset (`customrecord_nx_asset`).	Identifies the equipment or site associated with the sales activity.
Case	Opportunity Field Service Case (`custbody_nx_case`) references Case (`supportcase`).	Associates the opportunity with a service request. A case separately stores its selected transaction in Field Service Transaction (`custevent_nx_case_transaction`). These are separate references.
CRM Task	Opportunity Field Service Task (`custbody_nx_task`) references CRM Task (`task`).	Holds the service-task context and can supply the opportunity's asset.
Project Task	Opportunity Field Service Project Task (`custbody_nx_projecttask`) references Project Task (`projecttask`).	Holds a separate project-task context. The FSM model includes this mapping when Project Management is enabled.

Related Record

Relationship and Field ID

Purpose

Customer or Project

Opportunity native Entity (entity) holds the transaction's entity. Without NetSuite Project Management, this can identify a project, whose customer supplies the FSM Customer.

Provides the native sales context.

Customer

Opportunity Field Service Customer (custbody_nx_customer) references the customer.

Keeps the customer identifiable separately from a project used as Entity.

Project

With Project Management enabled, opportunity native Project (job) holds the project. Without it, the FSM Project mapping writes to entity.

Associates the potential sale with a project using the account's native relationship.

Asset

Opportunity Field Service Asset (custbody_nx_asset) references Field Service Asset (customrecord_nx_asset).

Identifies the equipment or site associated with the sales activity.

Case

Opportunity Field Service Case (custbody_nx_case) references Case (supportcase).

Associates the opportunity with a service request. A case separately stores its selected transaction in Field Service Transaction (custevent_nx_case_transaction). These are separate references.

CRM Task

Opportunity Field Service Task (custbody_nx_task) references CRM Task (task).

Holds the service-task context and can supply the opportunity's asset.

Project Task

Opportunity Field Service Project Task (custbody_nx_projecttask) references Project Task (projecttask).

Holds a separate project-task context. The FSM model includes this mapping when Project Management is enabled.

Field Service Customer is synchronized with native Entity by the standard Opportunity model. Customer and asset eligibility, sourcing, and reconciliation are described in FSM Customer and Asset Selection.

An asset reference on an opportunity doesn't change the customer stored on the asset. Additional account custom links don't automatically add opportunity data to FSM Asset inheritance, FSM Mobile resources, history, reports, or synchronization.

FSM Fields

These fields provide the opportunity's service context. The following table uses the supplied English field labels. Account forms can use different labels.

Field	Field ID	Purpose	Important Values or Behavior
Native Entity	`entity`	Customer or project context for the sales record.	FSM reconciles it with Field Service Customer. A project used as Entity supplies its customer when Project Management is not enabled.
Native Project	`job`	Separate project relationship when Project Management is enabled.	Without that feature, the FSM Project write destination is `entity`.
Field Service Customer	`custbody_nx_customer`	Customer for the service-related sale.	The Opportunity model sources this value and reconciles it with Entity. The value is not a fixed customer default.
Field Service Asset	`custbody_nx_asset`	Equipment or site associated with the opportunity.	An associated CRM task or project task can supply this value during FSM initialization and validation.
Field Service Case	`custbody_nx_case`	Related service request.	The field definition sources the case from the selected Field Service Task's native Case relationship. It doesn't itself create a case.
Field Service Task	`custbody_nx_task`	Related CRM task.	Separate from the opportunity's ordinary native activity attachments and from a project task.
Field Service Project Task	`custbody_nx_projecttask`	Related project task.	Project tasks and CRM tasks are different record types. The FSM model includes the Project Task mapping when Project Management is enabled.
Field Service Idempotency Key	`custbody_nx_idempotency_key`	Older custom creation-identity field retained for compatibility.	This field doesn't indicate sales status, recurrence completion, or successful processing. For the native External ID used in standard FSM Mobile record creation, see FSM Mobile Duplicate Creation Protection.

Field

Field ID

Purpose

Important Values or Behavior

Native Entity

entity

Customer or project context for the sales record.

FSM reconciles it with Field Service Customer. A project used as Entity supplies its customer when Project Management is not enabled.

Native Project

job

Separate project relationship when Project Management is enabled.

Without that feature, the FSM Project write destination is entity.

Field Service Customer

custbody_nx_customer

Customer for the service-related sale.

The Opportunity model sources this value and reconciles it with Entity. The value is not a fixed customer default.

Field Service Asset

custbody_nx_asset

Equipment or site associated with the opportunity.

An associated CRM task or project task can supply this value during FSM initialization and validation.

Field Service Case

custbody_nx_case

Related service request.

The field definition sources the case from the selected Field Service Task's native Case relationship. It doesn't itself create a case.

Field Service Task

custbody_nx_task

Related CRM task.

Separate from the opportunity's ordinary native activity attachments and from a project task.

Field Service Project Task

custbody_nx_projecttask

Related project task.

Project tasks and CRM tasks are different record types. The FSM model includes the Project Task mapping when Project Management is enabled.

Field Service Idempotency Key

custbody_nx_idempotency_key

Older custom creation-identity field retained for compatibility.

This field doesn't indicate sales status, recurrence completion, or successful processing. For the native External ID used in standard FSM Mobile record creation, see FSM Mobile Duplicate Creation Protection.

Opportunity mappings differ from the shared Transaction mappings. The standard Opportunity model removes inherited search mappings for created-from data, email, contact, and purchase-order reference. It also adapts its identity and Project mappings. A removed search mapping doesn't necessarily mean that the corresponding native field is absent. Use FSM Record Model Configuration - Opportunity for the applicable mappings.

Creation and Update Sources

The following sources affect the opportunity or its service references.

Source	Effect on the Record
NetSuite Opportunity entry	Creates or edits the sales record. FSM form handling offers customer and asset choices and reconciles related values when applicable.
Linked CRM Task or Project Task	Can supply Field Service Asset through FSM model initialization and validation. The supplied Case field definition also sources the selected CRM Task's Case.
Case relationship processing	A case can reference an opportunity in Field Service Transaction. When the case is created or its Company changes, relationship processing can request background updates to the opportunity's Case and Project relationships.

Source

Effect on the Record

NetSuite Opportunity entry

Creates or edits the sales record. FSM form handling offers customer and asset choices and reconciles related values when applicable.

Linked CRM Task or Project Task

Can supply Field Service Asset through FSM model initialization and validation. The supplied Case field definition also sources the selected CRM Task's Case.

Case relationship processing

A case can reference an opportunity in Field Service Transaction. When the case is created or its Company changes, relationship processing can request background updates to the opportunity's Case and Project relationships.

The opportunity form uses Field Service User Event (customscript_nx_userevent, deployment customdeploy_nx_opportunity_userevent) and Field Service Client (customscript_nx_client, deployment customdeploy_nx_opportunity_client). For shared script identities and execution guidance, see FSM Script Reference.

Case-driven transaction updates are separate from saving the case. Check the saved Case and Project relationships on the opportunity to confirm the result. A completed execution alone doesn't confirm that every related update succeeded. See FSM Related Service Work.

Used by FSM Features

These capabilities use the opportunity's service relationships.

Feature	How the Record Is Used
FSM Customer and Asset Selection	Offers related customer and asset choices and reconciles the transaction's service context.
FSM Related Service Work	Can update the Case and Project relationships on the transaction selected by a case.

Feature

How the Record Is Used

FSM Customer and Asset Selection

Offers related customer and asset choices and reconciles the transaction's service context.

FSM Related Service Work

Can update the Case and Project relationships on the transaction selected by a case.

Record Constraints and Data Requirements

Opportunity records require the Opportunities feature. To enable it, go to Setup > Company > Enable Features. On the CRM subtab, under Sales, check the Opportunities box. See Opportunity.

FSM supplies six stored custom body fields for opportunity records. None is marked required in the supplied definitions or has a fixed initial selection or text value. Forms or account validation can impose additional requirements, and sourced values remain separate from fixed defaults.

A custom FSM Mobile Opportunity resource doesn't automatically inherit the standard Quote resource's specialized synchronization and conversion behavior. Adding a relationship or copying a resource definition doesn't establish equivalent processing.