FSM Estimate Record

An estimate records proposed items, quantities, and prices for a customer. Field Service Management (FSM) uses the standard NetSuite estimate record for the quotes prepared in FSM Mobile. Quote is the name used in FSM Mobile for this record, not a separate FSM custom record.

The estimate connects quoted work to its customer, project, case, asset, and tasks where those relationships apply. A sales order created from an estimate is a separate transaction and retains a reference to the source estimate. Estimates are nonposting transactions. For more information, see Estimates.

Record Information

Use these identifiers when working with record mappings, searches, and integrations. Field labels can vary by account and form.

Property

Value

Record type

Standard NetSuite transaction

Record name

Estimate (called Quote in FSM Mobile)

SuiteScript record type ID

estimate

FSM Mobile resource ID

quote

FSM NetSuite record model

models/quote, which inherits models/transaction

Supplied FSM transaction form

Field Service Quote (custform_nx_estimate)

Record identity

Internal ID (internalid) identifies the record. Estimate # (tranid) is the displayed transaction number.

The standard Quote search in FSM Mobile restricts the transaction's recordtype to estimate. The resource ID quote and model name models/quote are FSM identifiers, not alternative NetSuite record type IDs. For native scripting support, see Estimate.

Forms

The supplied Field Service Quote form presents the FSM Customer, Asset, Task, Case, and Project Task fields in its service details group. It also includes Customer Signature. Account-created estimate forms can arrange these fields differently. The product definition doesn't mark the supplied form as preferred. The account's form preferences and the form selected for entry determine which form appears when you create an estimate.

NetSuite always stores the custom form used for an estimate with that transaction. NetSuite displays the stored form rather than the preferred form when you view or edit the estimate. The Store Form with Record checkbox is not available for estimate forms. See Storing Custom Forms with Transactions.

Estimates created through models/quote can use a configured custom-form default. This default doesn't change the form on existing estimates or determine which Quote screen appears in FSM Mobile. For information about configuring the custom-form default, see Custom Forms for Record Creation.

The standard FSM Mobile Quote tab defines its elements directly. It doesn't generate them from the estimate's stored transaction form. Its field visibility, initial values, and requirements therefore differ from the NetSuite form. Automatic loading of custom transaction forms into FSM Mobile is not officially supported. For more information, see the Custom Forms section of Mobile App and Configuring FSM Mobile Quote Management.

Record Relationships

Transaction-level fields describe the estimate's service context. Item-line fields identify the work associated with an individual quoted line. The line relationships are separate from the transaction-level relationships.

Related Record

Relationship and Field ID

Purpose

Customer

The estimate stores native Entity (entity) and Field Service Customer (custbody_nx_customer).

Keeps the service customer identifiable separately when the native relationship contains a project. FSM synchronizes the Customer and Entity according to the account's Project Management features.

Project

When Project Management is enabled, the estimate stores the native project relationship in job. Otherwise, FSM uses entity. Transaction searches can read the project through job.internalid.

Associates the quote with the wider job. This is a native relationship, not a supplied custom FSM project field.

Case

The estimate stores Field Service Case (custbody_nx_case). Separately, the case stores its selected transaction in Field Service Transaction (custevent_nx_case_transaction).

Connects the estimate to a service request. Field Service Transaction identifies one selected transaction on the case. It doesn't list all estimates that reference the case.

Asset

The estimate stores Field Service Asset (custbody_nx_asset). Each item line can store Field Service Asset (trans) (custcol_nx_asset).

Identifies the service asset at transaction and line level. Linking an item on a quote doesn't create an FSM asset.

CRM Task

The estimate stores Field Service Task (custbody_nx_task). Each item line can store Field Service Task (trans) (custcol_nx_task).

Identifies the service visit associated with the quote and its individual lines. A task can have several quotes.

Project Task

The estimate stores Field Service Project Task (custbody_nx_projecttask). Each item line can store Field Service Project Task (trans) (custcol_nx_projecttask).

Provides the corresponding links for the separate project task record type. A project task is not a CRM task.

Item

Each estimate item line stores its item reference in the native item sublist's item field.

Identifies the quoted product or service. One estimate can contain several item lines.

Sales Order

The resulting sales order stores native Created From (createdfrom) referencing the estimate.

Identifies the source of the converted order. The estimate remains a separate record.

Applying a quote in FSM Mobile can set the case's selected transaction. When FSM creates a sales order from that selected estimate, it can replace the case's selection with the new order. The estimate's Field Service Case field and the case's Field Service Transaction field remain separate relationships. See FSM Mobile Quote Management.

An account custom link remains a separate relationship. Adding it doesn't automatically include the linked record in FSM inheritance, FSM Mobile selection, history, reports, or synchronization.

FSM Fields

The following fields are useful for interpreting estimate data in FSM. The table uses the English labels from the supplied custom-field definitions. Shorter labels can appear on the FSM form.

Transaction-Level Service Fields

These fields are stored on the estimate itself. The supplied custom-field definitions don't require values in these fields.

Field

Field ID

Purpose

Important Values or Sources

Field Service Customer

custbody_nx_customer

Customer for the service work.

The standard FSM Mobile creation defaults supply the task's customer. The Quote model also reconciles this value with native Entity.

Field Service Asset

custbody_nx_asset

Primary service asset associated with the transaction.

FSM transaction-model validation can source it from the linked CRM task or project task. This is distinct from the asset on each item line.

Field Service Task

custbody_nx_task

Reference to a CRM task.

The standard FSM Mobile creation defaults supply the current CRM task where applicable.

Field Service Project Task

custbody_nx_projecttask

Reference to a project task.

The standard FSM Mobile creation defaults supply the current project task where applicable.

Field Service Case

custbody_nx_case

Reference to a case.

Its supplied field definition sources the case from Field Service Task's native Case relationship. Case-related processing can also maintain this link.

Field Service Customer Signature

custbody_nx_customer_signature

Rich-text storage for the quote's customer signature content.

Used by the NetSuite signature control and FSM Mobile Quote signing. A stored signature alone is not proof that a sales order exists. For conversion conditions, see FSM Mobile Quote Management.

Field Service Idempotency Key

custbody_nx_idempotency_key

Creation-identity field retained for compatibility and visibility.

Current standard FSM Mobile record creation uses native External ID instead. It is not an estimate processing or conversion status.

For customer and asset reconciliation and selection, see FSM Customer and Asset Selection. For the signature control, see FSM NetSuite View Configuration - views/signature.

Item-Line Service Fields

These supplied transaction columns apply to sales lines. A line can retain its own references even when its transaction-level service context is different.

Field

Field ID

Purpose

Important Values or Sources

Field Service Task (trans)

custcol_nx_task

CRM task associated with the line.

New standard FSM Mobile quote lines receive the current CRM task.

Field Service Project Task (trans)

custcol_nx_projecttask

Project task associated with the line.

New standard FSM Mobile quote lines receive the current project task where applicable.

Field Service Asset (trans)

custcol_nx_asset

Asset associated with the line.

Standard FSM Mobile line defaults use the task's asset. The supplied column also sources the asset from the line's CRM task.

Field Service Case (trans)

custcol_nx_case

Case associated with the line.

The supplied column sources the case from the line's CRM task. The standard Quote resource doesn't submit a separate Case-column mapping.

Field Service Consumable

custcol_nx_consumable

Reference to a Field Service Consumable record.

The standard Quote resource doesn't create consumable records or include this column in its line mapping.

A value in Field Service Consumable doesn't confirm recorded item usage or fulfillment.

Line task references also participate in FSM Mobile line ownership checks. Editing and deletion consequences are explained in Quote Actions and Restrictions.

Native Fields Used by Quote

Native NetSuite data supplies the quote's identity, transaction details, amounts, and email request. FSM Mobile element names can differ from the underlying field IDs.

Field or Value

Field ID

Meaning in FSM

Estimate #

tranid

Saved transaction number displayed in FSM Mobile. Separate from internalid.

Date

trandate

Estimate transaction date. Standard FSM Mobile creation uses the current task's date.

PO/Check #

otherrefnum

Customer's purchase-order reference text, displayed as Purchase Order in FSM Mobile. It is not a relationship to a NetSuite purchase order record.

To Be Emailed, Email

tobeemailed, email

Email request and recipients. FSM Mobile maps these to Send Email and Emails. They are not email-delivery status fields.

Subsidiary

subsidiary

Transaction subsidiary. Standard FSM Mobile creation supplies the task's subsidiary explicitly when Multi-Subsidiary Customer is enabled.

Custom Form

customform

NetSuite form associated with the transaction. Separate from the FSM Mobile resource's element definitions.

Estimate status (search value)

status

Saved transaction status displayed read-only by FSM Mobile. It describes the estimate's business state, not a script execution. The initial FSM Mobile label Open is not confirmation of a saved status.

Total

total

Saved NetSuite transaction total, displayed read-only by FSM Mobile.

Item, Quantity, Description

item.item, item.quantity, item.description

Quoted line data in the native Item sublist. The standard transaction search reads description from memo.

Line Amount (search value)

amount

Amount returned for the saved transaction line. The standard Quote mapping reads this value but doesn't specify a field to write it to.

Line identity

line in searches and item.line in the Quote map

Identifies an existing item line during synchronization. Separate from the parent estimate's internal ID.

External ID

externalid

Native record identity used by current standard FSM Mobile creation to recognize repeated requests, with the fsm_ identity prefix. Separate from the Field Service Idempotency Key field.

NetSuite supplies the saved pricing and totals. The standard FSM Mobile Quote tab has no rate-entry field, price-level selector, or currency selector. See Rates and Price Levels for pricing boundaries and Preparing an Estimate for native transaction fields.

Creation and Update Sources

These sources can create or change estimate data and related links. Saving locally, saving in NetSuite, and creating a related transaction are separate results.

Source

Effect on the Record

Native NetSuite Estimate entry

Creates or edits the estimate using the selected transaction form. Applicable FSM form and record handling maintain service data.

FSM Mobile Quote creation

Synchronization creates an estimate using the supplied Customer, date, task context, and quoted lines. Standard FSM Mobile creation identity is stored in External ID.

FSM Mobile Quote update

Synchronization saves mapped estimate changes. A qualifying signed update can create a separate sales order from the estimate. The Quote response reloads the estimate.

Apply to current Job in FSM Mobile

Can associate the estimate with the task's project and set the case's selected transaction where those records exist.

FSM transaction-model validation

Reconciles Field Service Customer with Entity and can source Asset and email from linked service records.

Case-related background updates

Can update a selected transaction's case and project relationships after case changes. Saving the case doesn't establish that this later update has completed.

See FSM Mobile Quote Management for the signed-update conditions and transaction outcomes, and FSM Related Service Work for case-related updates.

Used by FSM Features

These capabilities use the estimate's data and relationships. For detailed behavior and limits, see the linked feature topics.

Feature

How the Record Is Used

FSM Mobile Quote Management

Stores FSM Mobile quotes and supplies the source estimate for signed conversion to a sales order.

FSM Customer and Asset Selection

Uses transaction-level Customer and Asset fields on NetSuite forms.

FSM Related Service Work

Maintains a case's selected transaction and associated project and case context through the relevant related-record actions.

FSM Mobile Duplicate Creation Protection

Uses the estimate's creation identity for repeated standard FSM Mobile creation requests.

Record Constraints and Data Requirements

The supplied Field Service Quote form requires native Customer (entity), Date (trandate), and Custom Form (customform). Its FSM service fields and the supplied FSM custom-field definitions are not required. Account-created forms and other account rules can impose additional requirements. Not every native estimate requires a case, asset, project, or task link.

The standard FSM Mobile Quote tab separately requires Items and Emails, and requires an Item and Quantity in each row. The default Quantity for a new line is 1. The selected shared item option determines the minimum quantity. The Emails field initially uses the email address from the task context and remains required when the Send Email box is cleared. These are FSM Mobile requirements and defaults, not universal estimate-field rules. For configuration details, see Configuring FSM Mobile Quote Management.

The FSM Mobile Quote capability is intended for noninventory item quotes. A native estimate's ability to contain other item types doesn't establish support for those types through FSM Mobile Quote. Signature content, a refreshed total, or an email request doesn't by itself establish conversion, fulfillment, or delivery. For conversion, fulfillment, and delivery outcomes, see FSM Mobile Quote Management.

Additional Information

Related Topics

General Notices