FSM Asset Record

An asset in Field Service Management (FSM) is a custom NetSuite record for a service site, machine, component, or other asset. It identifies equipment or locations requiring installation, service, repair, or maintenance. It connects the equipment or service location to its customer and to related service work.

The asset stores its own identity, relationships, address, coordinates, and time zone. A parent asset can group other assets into a hierarchy. Features use these values for selection, service-location sourcing, related work, and background processing.

Record Information

The following identifiers are useful when working with searches, field mappings, and integrations.

Property	Value
Record type	FSM custom record
Record name	Field Service Asset
Record ID	customrecord_nx_asset
Record identity	NetSuite Internal ID (internalid)
Display name	Name (name). FSM can generate this through automatic naming
Record model	models/asset

Name and Serial provide descriptive information about the asset. To identify a saved asset, use its NetSuite Internal ID. For naming rules and supported changes, see FSM Automatic Record Naming.

Forms for NetSuite and FSM Mobile

Separate forms let NetSuite and FSM Mobile present different fields from the same asset data. Use custom forms to present the fields relevant to different asset types. For example, a Site form can emphasize the service address and regional information. A Machine form can emphasize equipment identity and technical details.

For forms used in the NetSuite UI, check the Store Form with Record box. NetSuite then retains the form used to create the asset and uses it when that record is viewed or edited, rather than using the preferred form. Choose the appropriate form when creating the asset. For the setting's standard behavior, see Custom Entry Form Properties.

Create separate custom forms for FSM Mobile, with Store Form with Record cleared. Reference these forms in the FSM Mobile resource configuration to show only the fields relevant to technicians in the field. FSM Mobile forms can also differ by asset type where the configuration selects the appropriate form.

Selecting a form to generate fields for an FSM Mobile resource doesn't determine which NetSuite form is stored with the asset. For supported form loading and field overrides, see FSM Mobile Resource Properties Reference.

Record Relationships

The relationship is stored on the record that references the other record. For example, the asset stores its customer link, and a project stores its asset link.

Related Record	Relationship and Field ID	Purpose
Customer	Asset Customer (custrecord_nx_asset_customer) references the primary customer	Identifies the asset owner and supplies the customer address-book choices.
Additional Customers	Asset Field Service Customers (custrecord_nx_asset_customers) is a Customer multi-select	Stores additional customer relationships. To use these customers for service selection, configure the selection rules described in FSM Customer and Asset Selection.
Item	Asset Item (custrecord_nx_asset_item) references an item	Identifies the item represented by the asset. Item data can supply a description, image, and setup used by associated features.
Parent Asset	Asset Parent (parent) references another FSM asset record	Forms the asset hierarchy. Each child has an immediate parent. An asset can be both a child and a parent.
Asset Type	Asset Type (custrecord_nx_asset_type) references customrecord_nx_asset_type	Classifies the asset. Standard types include Site, Machine, and Component.
Customer address	Asset Address Select (custrecord_nx_asset_address) identifies an address-book entry	Supplies address text from the primary customer's address book.
Project	Project Field Service Asset (custentity_nx_asset) references the asset	Associates a project, including a warranty or other dated service context, with the asset. More than one project can reference an asset.
Case	Case Field Service Asset (custevent_nx_case_asset) references the asset	Identifies the primary asset for the case. Case Field Service Assets (custevent_nx_assets) can identify additional child assets.
CRM Task or Project Task	Field Service Task Asset (custevent_nx_task_asset) references the asset	Identifies the asset being serviced and provides a service-location source.
Transaction	Asset Transaction (custrecord_nx_asset_transaction) references a transaction	Retains the transaction reference supplied by fulfillment asset processing. Transaction body and line asset references (custbody_nx_asset, custcol_nx_asset) are separate relationships.
Maintenance or Repair record	Maintenance Asset (custrecord_nx_maintenance_asset) or Repair Asset (custrecord_nx_repair_asset) references the asset	Associates a service record with the equipment or location being maintained or repaired. These records also have separate links to the related project, case, CRM task, and project task.
Time entry	Field Service Asset (custcol_nx_asset) on the time entry references the asset	Associates recorded time with the asset being serviced.
Consumable record	Consumable Asset (custrecord_nx_consasset) references the asset	Associates consumed items with the asset being serviced.
Sales Order line	Field Service Asset (custcol_nx_asset) on the line references the asset	Associates an individual line with an asset. The line relationship can differ from the transaction body's asset relationship.

Assets and Service Records

The asset identifies the equipment or service location. Related inspection, maintenance, or repair records can capture the work performed against that asset and link it to the relevant case, task, or project. This separates the asset's descriptive information from records of individual service activities.

For example, a solution can retain a separate inspection record for each machine visit and keep the same asset record for that machine. The checklist's configuration determines its record links and how many entries are required or permitted. An asset relationship alone doesn't enforce one checklist per visit.

Asset links also provide context for recorded time, consumed materials, and service history. The standard History resource in FSM Mobile retrieves completed CRM tasks for the selected asset and related sales order item lines. It also retrieves completed project tasks when Project Management is enabled. Which records appear in a history view depends on its configured searches; linking a custom record to an asset doesn't automatically add it to FSM Mobile history or a service report.

Parent Relationships and Inheritance

NetSuite parent-record relationships and FSM field inheritance serve different purposes. The asset definition marks Customer, Item, and Transaction as parent-record links, allowing the asset to appear as a child in the related record's sublist. These links don't mean that the Customer, Item, or Transaction is the asset's equipment parent.

The asset's Parent (parent) field forms the hierarchy between assets. FSM inheritance uses this immediate parent to supply configured field values on the child. The default inherited fields are Customer, Address Select, Address, and Region. Latitude, Longitude, and Time Zone are not part of that default list.

A parent relationship doesn't by itself define which values inherit. See FSM Asset Hierarchy and Inheritance for behavior and Configuring FSM Asset Hierarchy and Inheritance for field choices. For information about the underlying custom-record relationships in NetSuite, see Custom Record Type Fields that Affect Parent-Child Relationship on Custom Record.

Other Custom-Record Relationships

Accounts can extend the asset's relationships using other custom record types. For example, a solution can represent a machine's components as child FSM assets, or use a separate custom component record type with a field that references the machine's asset. A NetSuite parent-record relationship can display those custom component records in a related sublist on the asset. See One Parent Record Type to One Child Record Type for the underlying relationship.

A Site → Machine → Component asset hierarchy is one design option. A Site → Machine asset hierarchy with separate custom component records is another.

A key design consideration is whether each component or related record needs its own service context in FSM Mobile, particularly checklists completed against that individual component or record. These requirements differ from simply recording information about the asset's composition.

Requiring a checklist against each component doesn't necessarily require a separate FSM Mobile tab for every component. Depending on the configured solution, technicians may complete records beneath individual Asset tabs or select the relevant asset within a shared checklist tab. Consider the required record relationships separately from how those records should be presented on FSM Mobile.

If components primarily describe an asset's contents, consider linking separate custom component records to the asset. This approach can simplify the hierarchy and reduce the number of FSM asset records created only to describe components. Where component-specific checklists or FSM Mobile interactions are required, consider how each design will support those requirements.

A custom component record linked to an asset remains a different record type. The relationship alone doesn't give it FSM asset inheritance or include it in features that expect an FSM asset. Any additional behavior or integration must be designed separately.

FSM Mobile grouping can also differ from the asset hierarchy. For example, a custom solution can keep Machine and Component assets as direct children of a Site. A separate custom relationship can associate each Component with a Machine. FSM Mobile can group the Components beneath that Machine. FSM's standard inheritance still follows the asset's Parent field. The additional grouping relationship doesn't replace it.

Other custom links can connect an FSM asset to records used for a different purpose. For example, an account can link an FSM service asset to a separate Fixed Asset Management (FAM) record used for financial asset management. Such a link is an account customization, not a supplied asset field or automatic synchronization between the two records.

FSM Fields

These fields describe the asset and the context used by FSM. A field can contain a value even if a feature that uses it is disabled or related processing is incomplete. Because field labels can vary by account, use field IDs to identify the underlying fields.

Identity and Classification

Use these fields to identify the asset and distinguish its record identity from the matching values used by FSM.

Field	Field ID	Field Behavior
Name	name	Display name. Automatic naming can replace this value according to the asset model.
Parent	parent	Immediate parent asset. An empty value identifies an asset without an equipment parent.
Type	custrecord_nx_asset_type	Asset classification, such as Site, Machine, or Component.
Item	custrecord_nx_asset_item	Item represented by the Asset. Used with Serial, or with Address when Serial is empty, by the default matching definition.
Serial	custrecord_nx_asset_serial	Serial or other identifying text. The default matching definition combines it with Item. It doesn't establish global uniqueness of Serial alone.
Transaction	custrecord_nx_asset_transaction	Transaction associated with the asset through fulfillment processing. This field is a reference, not an asset processing status.

Customer and Service Location

The primary customer, additional customers, address selection, and saved geographic values are distinct data. A service location means the physical place where work occurs. It is not a required reference to a NetSuite location record.

Field	Field ID	Field Behavior
Customer	custrecord_nx_asset_customer	Primary customer or owner. The standard service-selection relationship uses this customer.
Field Service Customers	custrecord_nx_asset_customers	Additional customer references. The standard asset model doesn't use this field as its default list of permitted service customers. It doesn't expand Address Select.
Address Select	custrecord_nx_asset_address	Selects an entry from the customer's address book. When Address Select has a value, FSM uses that entry to supply the saved Address text.
Address	custrecord_nx_asset_address_text	Saved service-address text. It can be supplied by Address Select, Address Search, inheritance, or fulfillment processing.
Region	custrecord_nx_asset_region	Service-region classification. It is included in the standard inheritance list.
Latitude	custrecord_nx_asset_latitude	Saved geographic latitude used with Longitude to locate the asset.
Longitude	custrecord_nx_asset_longitude	Saved geographic longitude used with Latitude to locate the asset.
Geolocation	custrecord_nx_asset_geo_location	Combined coordinate text maintained by coordinate lookup, in latitude/longitude form. It is separate from the two coordinate fields.
Time Zone	custrecord_nx_asset_time_zone	Reference to an FSM Time Zone (customrecord_nx_time_zone). Provides the asset's service-time context. It is not proof that a physical-location lookup succeeded.

If a lookup doesn't replace the saved coordinates, the address text and coordinates can refer to different locations. Detailed sourcing and application rules belong to FSM Service Locations and Geocoding and FSM Service Time Zone Sourcing and Synchronization.

For the difference between an asset's owner and the customers permitted for service, see FSM Customer and Asset Selection. The asset model's mappings and customer-selection definitions are documented in FSM Asset Model Reference.

Processing and Compatibility Indicators

The asset has an indicator for pending location propagation. The following table explains the compatibility fields and why these values don't confirm that processing is running or complete.

Field	Field ID	Field Behavior
Update Location	custrecord_nx_asset_location_update	Requests background propagation to eligible related tasks after FSM detects an edit or inline update to Address, Latitude, or Longitude.
Geolocation Compliant	custrecord_nx_asset_geo_location_comp	Compatibility indicator used by earlier Google-data compliance processing. Its supplied checkbox default is checked. It doesn't establish coordinate accuracy, a successful lookup, or a running execution.
Time Zone Compliant	custrecord_nx_asset_timezone_comp	Compatibility indicator used by earlier Google-data compliance processing. Its supplied checkbox default is checked. It doesn't establish the correctness of the stored Time Zone or completion of current time-zone processing.
Idempotency Key	custrecord_nx_asset_idempotency_key	Compatibility field retained from earlier duplicate-creation protection. Current standard FSM Mobile record creation uses External ID instead. This field is not the asset's equipment identity or current standard FSM Mobile completion indicator.
External ID	externalid	Native record identity also used by standard FSM Mobile synchronization to recognize repeated creation requests. An FSM Mobile key can identify an earlier target record independently of Item/Serial matching.

FSM clears Update Location when an assessment finds no eligible task locations that differ from the asset's location. A checked box doesn't confirm that processing is running. A cleared box doesn't confirm that every historical task has the asset's current location.

The Update Child Assets message on an Asset page can reflect outstanding inheritance or task-location work. It is separate from Update Location and doesn't establish that an execution is running. FSM identifies pending inheritance work by comparing configured child values with the immediate parent's values. The asset has no dedicated checkbox that confirms inheritance is complete.

The asset definition has no direct Field Service Error reference field. Associated processing can record errors separately in the Field Service Error Record (customrecord_nx_error). A matching unrecovered processing error can prevent an individual update even when the asset remains eligible for processing. A completed script execution doesn't prove that every intended asset or task update succeeded. See the applicable Feature for processing consequences and FSM Script Reference for execution monitoring.

For the compatibility change and standard FSM Mobile identity, see FSM Mobile Duplicate Creation Protection.

Creation and Update Sources

The following sources can create, display, or change asset data. Their effects depend on the applicable feature and account setup.

Source	Record Effect
Manual NetSuite entry	Creates or edits an asset directly, including an asset created from a parent's child-asset sublist. FSM naming, inheritance, and location sourcing can apply during the save.
CSV import	Can create asset records. Available fields, permissions, import settings, and enabled script execution affect the result. Importing a record is not proof that geocoding or related background work completed.
Item Fulfillment	Submits asset rows for background creation or update. Matching rows update an existing asset. Unmatched rows create one. The fulfillment supplies Item, Serial, Customer, parent, address values, and the Transaction reference. Inherited values can take precedence over supplied row values.
Parent Asset and background inheritance	A child save sources configured fields from its immediate parent. Background processing can save selected children to refresh differing inherited values.
Address, coordinate, and time-zone sourcing	FSM can update saved address text, coordinates, combined Geolocation, and Time Zone through their separate sourcing paths. An asset location edit can also mark pending task-location propagation.
FSM Mobile	The standard Asset resource shows the selected task's asset or an available immediate child, plus a read-only item image and description. Resources configured for editing in the account can synchronize mapped asset fields. The standard display doesn't provide general asset editing.
Automatic Project creation	When an asset is created, FSM can request a linked project based on the item's setup. The project is a separate record. The request doesn't confirm that project creation is complete.

The asset form and inheritance use Field Service User Event (customscript_nx_userevent, asset deployment customdeploy_nx_asset_userevent) and Field Service Client (customscript_nx_client, asset deployment customdeploy_nx_asset_client). Background inheritance and task-location propagation use Field Service Scheduled : Asset (customscript_nx_scheduled, customdeploy_nx_asset). See FSM Script Reference for script identity and execution details.

Used by FSM Features

These capabilities use the asset's fields or relationships. Follow the links for their lifecycle, selection rules, processing effects, and limits.

Feature	Asset Use
FSM Asset Hierarchy and Inheritance	Organizes assets and supplies configured fields from the immediate parent.
FSM Asset Processing from Item Fulfillments	Creates or updates assets from submitted fulfillment rows.
Projects Created in Response to Asset Creation	Uses information from the asset and item to request a linked project with dates. Saving the asset doesn't confirm that the project was created.
FSM Customer and Asset Selection	Uses the asset owner or configured relationship to supply permitted service-customer choices.
FSM Related Service Work	Associates assets with projects, cases, and tasks.
FSM Service Locations and Geocoding	Maintains location values and supplies location data to related tasks.
FSM Service Time Zone Sourcing and Synchronization	Determines or sources service-time context from asset coordinates and related records.
FSM Maps and Location Tracking	Uses saved service coordinates for maps and navigation.
FSM Program	Uses related project and asset context in recurring service work. An asset alone doesn't define recurrence.

Record Constraints and Data Requirements

None of the 17 custom fields is required by the supplied asset definition. Required values depend on the form, import, related record, or feature validation. For example, the standard fulfillment asset sublist requires Serial even though the asset definition doesn't.

FSM's default matching key combines Item with Serial. If Serial is empty, the key combines Item with Address text. FSM normalizes apostrophes and line breaks for comparison. Customer, parent, and Type are not included in that default matching key. Matching validation can therefore find the same asset across different customer or parent contexts. Don't treat a changed owner or parent as creating a separate equipment identity.

Matching rules, display naming, and FSM Mobile request identity are separate mechanisms. Duplicate validation on the asset form or an applicable noninteractive submission doesn't establish a universal database uniqueness constraint. See FSM Asset Model Reference for the matching definitions and Configuring FSM Asset Processing from Item Fulfillments for their fulfillment use.

Configured inherited fields can replace child-specific values. Parent-only field rules can clear values on a child. These are FSM field rules, distinct from NetSuite parent relationships. See the hierarchy Feature and its Configuration topic before changing those rules.

Additional Information

• FSM Customer and Asset Selection
• FSM Asset Hierarchy and Inheritance
• FSM Asset Processing from Item Fulfillments

Related Topics

• FSM Records
• FSM Asset Type Record
• FSM CRM Task Record
• FSM Customer Record
• FSM Item Record

General Notices