FSM Note Record

A note records a titled message associated with another NetSuite record. Field Service Management (FSM) uses the standard NetSuite note record for text entered in the FSM Mobile Notes tab. Several notes can belong to the same task, with each note retaining its own author, date, title, and message.

Notes are separate from the task's description, Field Service Actions Taken, and Field Service Internal Note fields. The Files resource in FSM Mobile handles photos and file attachments as separate records rather than note messages.

Record Information

Use these identifiers to distinguish the record, its presentation in FSM Mobile, and the data returned by searches.

Property	Value
Record type	Standard NetSuite
Record name	Note (displayed as User Notes on related records)
Record ID	`note`
Record identity	NetSuite Internal ID (`internalid`)
FSM Mobile resource ID	`notes` under `routes/mobile`
Related-task search join	`usernotes` is the search join. The standard resource retrieves note IDs through `usernotes.internalid`.

Property

Value

Record type

Standard NetSuite

Record name

Note (displayed as User Notes on related records)

Record ID

note

Record identity

NetSuite Internal ID (internalid)

FSM Mobile resource ID

notes under routes/mobile

Related-task search join

usernotes is the search join. The standard resource retrieves note IDs through usernotes.internalid.

notes is the resource name in FSM Mobile, and usernotes is a search join. Neither is a substitute for the record ID note. For native scripting support, see Note.

Forms

NetSuite uses the Standard Note Form for note popup windows unless an account has selected a preferred custom note form. Account-created forms can change field visibility, labels, order, and actions. You can select a form from the Custom Form list when the list is available. For more information, see Using Custom Note Forms and Creating Custom Note Forms.

The standard FSM Mobile Notes resource supplies its own Title, Message, and hidden Date elements. The resource doesn't load fields from a NetSuite note form, so changing the preferred form doesn't change these standard FSM Mobile elements. For form-generated fields in FSM Mobile and resource overrides, see Form Properties.

Record Relationships

The note holds its task, author, and asset references. The task association and asset association have different purposes.

Related Record	Relationship and Field ID	Purpose
Current task	The standard creation default in FSM Mobile supplies the task's internal ID to the note's native CRM/Support Record association, `activity`. Reading uses the task's `usernotes` search join.	Associates the message with the task being worked on. A task can have several notes.
Employee	The note's Author field (`author`) references the employee. Standard creation in FSM Mobile sets this field to the current user.	Identifies the note's author, separately from the task's primary assignee or additional team.
Field Service Asset	The note's Field Service Asset field (`custrecord_nx_asset`) references one asset (`customrecord_nx_asset`). FSM supplies this field.	Identifies the asset context for the note. FSM Mobile defaults it to the requested asset, when supplied, or the current task's asset. Several notes can reference the same asset.

Related Record

Relationship and Field ID

Purpose

Current task

The standard creation default in FSM Mobile supplies the task's internal ID to the note's native CRM/Support Record association, activity. Reading uses the task's usernotes search join.

Associates the message with the task being worked on. A task can have several notes.

Employee

The note's Author field (author) references the employee. Standard creation in FSM Mobile sets this field to the current user.

Identifies the note's author, separately from the task's primary assignee or additional team.

Field Service Asset

The note's Field Service Asset field (custrecord_nx_asset) references one asset (customrecord_nx_asset). FSM supplies this field.

Identifies the asset context for the note. FSM Mobile defaults it to the requested asset, when supplied, or the current task's asset. Several notes can reference the same asset.

An asset link doesn't replace the task association. The standard Notes resource finds note IDs attached to the current task and authored by the current user, then retains the notes whose asset matches the requested asset or the task's asset. It is not a list of every note on the customer, case, project, or asset.

NetSuite can also associate notes with other native or custom records. Those associations don't automatically make the notes available in this resource in FSM Mobile. A custom relationship in an account doesn't automatically include a note in FSM asset inheritance, history in FSM Mobile, service reports, or synchronization. Resource selection and mappings are described in FSM Mobile Resource Selection and Shared Data and FSM Searches and Field Mapping.

FSM Fields

These native and supplied FSM fields are useful when interpreting note data. Element names in FSM Mobile can differ from their stored field IDs.

Field	Field ID	Purpose	Usage Notes
Internal ID - standard	`internalid`	Identifies the saved note.	Separate from its title and from a new entry's local identity in FSM Mobile.
Title - standard	`title`	Short description of the note.	Mapped to Title in FSM Mobile (`title`). The standard element in FSM Mobile requires Title. The native Records Browser doesn't mark Title as required.
Memo - standard	`note`	Stores the message content.	Mapped to Message in FSM Mobile (`body`). Required by the native record definition and the standard element in FSM Mobile.
Date - standard	`notedate`	Date recorded for the note.	Mapped to Date in FSM Mobile (`date`) for reading only. The hidden element in FSM Mobile initially uses the current task's date; its standard mapping doesn't write that value to Note Date.
Author - standard	`author`	Employee credited with the note.	Standard creation in FSM Mobile defaults to the current user. No Author input is supplied in the standard Notes resource.
CRM/Support Record association - standard	`activity`	Identifies the task associated with a note in FSM Mobile.	Standard creation in FSM Mobile supplies the current task's internal ID. It is not a link to the FSM Field Service Activity time-tracking record.
Field Service Asset	`custrecord_nx_asset`	Stores the note's asset context.	Supplied, stored List/Record field. The field definition doesn't require a value or provide a default. The resource's `article` configuration supplies the default during creation in FSM Mobile.
External ID - standard	`externalid`	Technical identity used by standard record creation in FSM Mobile.	FSM stores the entry's creation key with the `fsm_` prefix. See FSM Mobile Duplicate Creation Protection.
Field Service Idempotency Key	`custrecord_nx_note_idempotency_key`	Older custom identity field retained for compatibility and visibility.	Not required for current standard creation in FSM Mobile, which uses External ID. It is not a note-completion or script-running indicator.

Field

Field ID

Purpose

Usage Notes

Internal ID - standard

internalid

Identifies the saved note.

Separate from its title and from a new entry's local identity in FSM Mobile.

Title - standard

title

Short description of the note.

Mapped to Title in FSM Mobile (title). The standard element in FSM Mobile requires Title. The native Records Browser doesn't mark Title as required.

Memo - standard

note

Stores the message content.

Mapped to Message in FSM Mobile (body). Required by the native record definition and the standard element in FSM Mobile.

Date - standard

notedate

Date recorded for the note.

Mapped to Date in FSM Mobile (date) for reading only. The hidden element in FSM Mobile initially uses the current task's date; its standard mapping doesn't write that value to Note Date.

Author - standard

author

Employee credited with the note.

Standard creation in FSM Mobile defaults to the current user. No Author input is supplied in the standard Notes resource.

CRM/Support Record association - standard

activity

Identifies the task associated with a note in FSM Mobile.

Standard creation in FSM Mobile supplies the current task's internal ID. It is not a link to the FSM Field Service Activity time-tracking record.

Field Service Asset

custrecord_nx_asset

Stores the note's asset context.

Supplied, stored List/Record field. The field definition doesn't require a value or provide a default. The resource's article configuration supplies the default during creation in FSM Mobile.

External ID - standard

externalid

Technical identity used by standard record creation in FSM Mobile.

FSM stores the entry's creation key with the fsm_ prefix. See FSM Mobile Duplicate Creation Protection.

Field Service Idempotency Key

custrecord_nx_note_idempotency_key

Older custom identity field retained for compatibility and visibility.

Not required for current standard creation in FSM Mobile, which uses External ID. It is not a note-completion or script-running indicator.

Note Date is separate from the task's scheduled date, its actual completion time, and the time when synchronization in FSM Mobile succeeds. The standard Notes resource has no separate note-level processing-complete or execution-status field.

For the native fields and requirements, see the NetSuite Note Records Browser. For read-only mappings, see Reading and Saving Different Fields.

Creation and Update Sources

You can manage notes in NetSuite or through an available resource in FSM Mobile. A successful local save doesn't confirm that the note is saved in NetSuite.

Source	Record Effect
NetSuite note entry	Creates or edits a note associated with a record through the available note form and permitted actions. A note entered here appears in the standard Notes resource in FSM Mobile only when it meets that resource's task, author, and asset selection.
FSM Mobile Notes	Creates, edits, or deletes notes where the resource is selected and its actions are available. Creation supplies the current user, task, and asset context. Title and Message use their field mappings.
Synchronization in FSM Mobile	Sends the saved local entry to the server, creates or updates the note in NetSuite, and returns its NetSuite identity.

Source

Record Effect

NetSuite note entry

Creates or edits a note associated with a record through the available note form and permitted actions. A note entered here appears in the standard Notes resource in FSM Mobile only when it meets that resource's task, author, and asset selection.

FSM Mobile Notes

Creates, edits, or deletes notes where the resource is selected and its actions are available. Creation supplies the current user, task, and asset context. Title and Message use their field mappings.

Synchronization in FSM Mobile

Sends the saved local entry to the server, creates or updates the note in NetSuite, and returns its NetSuite identity.

Defining the notes resource doesn't make it visible for every task. The applicable event resource rule must select it, and configured resource permissions and dependencies determine the available actions. See FSM Mobile Resource Selection and Shared Data.

Saving a note doesn't complete the task or create a Field Service Activity record for time tracking.

Used by FSM Features

These capabilities use the note's data or its standard creation path.

Feature	Record Use
Notes Tab in FSM Mobile	Captures and displays task-related messages through the `notes` resource.
FSM Mobile Duplicate Creation Protection	Recognizes repeated creation requests for the same entry using standard synchronization identity. It doesn't compare titles or message text to find similar notes.

Feature

Record Use

Notes Tab in FSM Mobile

Captures and displays task-related messages through the notes resource.

FSM Mobile Duplicate Creation Protection

Recognizes repeated creation requests for the same entry using standard synchronization identity. It doesn't compare titles or message text to find similar notes.

Record Constraints and Data Requirements

The native note record requires Memo (note). The standard Notes resource in FSM Mobile additionally requires Title. These requirements in FSM Mobile don't establish that every NetSuite note form has the same validation.

The supplied field definitions don't require values for Field Service Asset or the older Field Service Idempotency Key. A native note can therefore exist without an asset link, but its presence in FSM Mobile remains subject to the resource's selection rules.

Action permissions in FSM Mobile and successful validation don't replace NetSuite data-access and save requirements. A hidden field is a presentation choice, not a change to its stored identity or access permissions.