FSM Activity Record

In Field Service Management (FSM), a Field Service Activity records a service-time event. Examples include starting or completing a customer relationship management (CRM) task. It stores the event's date, time, activity type, employee, and task, along with available location coordinates and details.

FSM uses activity entries as input to automatic service time tracking. Activity entries record events, and separate NetSuite time bills record the resulting employee time and duration.

Record Information

Use the record and field IDs to identify the data when account labels or forms differ.

Property	Value
Record type	FSM custom record
Record name	Field Service Activity
Record ID for NetSuite records and searches	`customrecord_nx_activity`
Saved record identity	NetSuite Internal ID (`internalid`)
FSM service endpoint	`/activity` and `/activity/{id}`

Property

Value

Record type

FSM custom record

Record name

Field Service Activity

Record ID for NetSuite records and searches

customrecord_nx_activity

Saved record identity

NetSuite Internal ID (internalid)

FSM service endpoint

/activity and /activity/{id}

The native NetSuite activity category and the FSM base model models/activity are separate from this custom record. The base model supplies shared behavior for CRM Tasks and Project Tasks and doesn't model Field Service Activity entries. For more information, see FSM Activity Base Model Reference.

Forms

The supplied FSM Task form (custform_nx_task) includes the related Field Service Activity sublist. Its entries are connected through the Activity's Task field. Account-created Task forms can present these related entries differently.

For information about viewing entries and opening an Activity's details from a Task, see Viewing Time Activities on Field Service Tasks.

When automatic tracking is enabled, FSM Mobile captures activities through the Start and Complete dialogs. The Update dialog updates a recorded start activity. These dialogs are separate from the NetSuite Activity form and from the FSM Mobile Time tab for manual time entry. Their fields are not generated by selecting a NetSuite Activity form. For more information, see FSM Service Time Tracking.

Record Relationships

Each reference in the following table links an Activity to one related record. Multiple Activity entries can refer to the same Task, Employee, Activity Type, or Time Zone.

Related record	Relationship and field ID	Purpose
CRM Task	Activity Task (`custrecord_nx_activity_task`) references the native Task (`task`). It is a supplied parent-record link.	Connects the event to the service visit and supports the Task's related Activity sublist.
Employee	Activity Employee (`custrecord_nx_activity_employee`) references an Employee (`employee`).	Identifies the employee recorded with the event. FSM Mobile supplies the signed-in employee.
Field Service Activity Type	Activity Type (`custrecord_nx_activity_type`) references `customrecord_nx_activity_type`.	Classifies the event, including the supplied Start Task and Complete Task types.
Field Service Time Zone	Activity Timezone (`custrecord_nx_activity_time_zone`) references `customrecord_nx_time_zone`.	Retains the time-zone reference supplied with the captured event.

Related record

Relationship and field ID

Purpose

CRM Task

Activity Task (custrecord_nx_activity_task) references the native Task (task). It is a supplied parent-record link.

Connects the event to the service visit and supports the Task's related Activity sublist.

Employee

Activity Employee (custrecord_nx_activity_employee) references an Employee (employee).

Identifies the employee recorded with the event. FSM Mobile supplies the signed-in employee.

Field Service Activity Type

Activity Type (custrecord_nx_activity_type) references customrecord_nx_activity_type.

Classifies the event, including the supplied Start Task and Complete Task types.

Field Service Time Zone

Activity Timezone (custrecord_nx_activity_time_zone) references customrecord_nx_time_zone.

Retains the time-zone reference supplied with the captured event.

An Activity Type classifies a captured event. The Task's Field Service Task Type (custevent_nx_task_type) classifies the service work and can supply its Service Time Item. These are different relationships.

The Activity has no supplied direct Case, Project, Asset, or Time Bill reference. Service context is available through its linked CRM Task. Resulting Time Bills store task links, including Field Service Task (custcol_nx_task). No supplied link connects a Time Bill to an individual Activity entry.

FSM Fields

The following table lists the supplied English labels for ten custom fields and the standard Inactive field. Labels and presentation can vary by account.

Field	Field ID	Purpose	Important values or behaviour
Date	`custrecord_nx_activity_date`	Date of the activity event.	Stored as a Date field, separately from Time. FSM Mobile supplies the current date when capturing a Start or Complete activity.
Time	`custrecord_nx_activity_time`	Clock time recorded for the activity event.	Stored as Time of Day. The FSM Mobile dialog supplies the user-confirmed time. Updating the start activity changes its time.
Timezone	`custrecord_nx_activity_time_zone`	Time-zone reference captured with the activity.	FSM Mobile supplies the selected task event's time-zone reference, including when its start activity is updated. This is not a duration or a UTC-offset field.
Type	`custrecord_nx_activity_type`	Activity classification.	The supplied types are Start Task (`starttask`) and Complete Task (`completetask`). These identifiers belong to Activity Type records, not to the Activity record itself.
Details	`custrecord_nx_activity_details`	Text associated with the event.	The standard Start and Complete capture paths in FSM Mobile leave Details empty. Automatic time processing can use a Complete activity's Details value as the Time Bill memo.
Employee	`custrecord_nx_activity_employee`	Employee associated with the event.	Separate from the Task's primary assignee and team. Automatic Time Bill employee selection uses the Task's assignment and team.
Task	`custrecord_nx_activity_task`	Related CRM Task.	Supplies the service-work relationship used to retrieve activities for time processing. It doesn't reference a Project Task.
Latitude	`custrecord_nx_activity_latitude`	Available latitude captured with the event.	A numeric coordinate for the employee position available to FSM Mobile when the event is captured. The value can be absent.
Longitude	`custrecord_nx_activity_longitude`	Available longitude captured with the event.	A numeric coordinate paired with Latitude. Its presence doesn't establish the position's age or accuracy.
Key	`custrecord_nx_activity_idempotency_key`	Identifier used by the dedicated Activity synchronization process.	The synchronization process stores the request's idempotency identifier and searches Key for an earlier submission. This key is separate from the saved record's Internal ID and from user authentication.
Inactive (standard)	`isinactive`	Native record inactivity.	Separate from task completion, synchronization success, and time-processing results.

Field

Field ID

Purpose

Important values or behaviour

Date

custrecord_nx_activity_date

Date of the activity event.

Stored as a Date field, separately from Time. FSM Mobile supplies the current date when capturing a Start or Complete activity.

Time

custrecord_nx_activity_time

Clock time recorded for the activity event.

Stored as Time of Day. The FSM Mobile dialog supplies the user-confirmed time. Updating the start activity changes its time.

Timezone

custrecord_nx_activity_time_zone

Time-zone reference captured with the activity.

FSM Mobile supplies the selected task event's time-zone reference, including when its start activity is updated. This is not a duration or a UTC-offset field.

Type

custrecord_nx_activity_type

Activity classification.

The supplied types are Start Task (starttask) and Complete Task (completetask). These identifiers belong to Activity Type records, not to the Activity record itself.

Details

custrecord_nx_activity_details

Text associated with the event.

The standard Start and Complete capture paths in FSM Mobile leave Details empty. Automatic time processing can use a Complete activity's Details value as the Time Bill memo.

Employee

custrecord_nx_activity_employee

Employee associated with the event.

Separate from the Task's primary assignee and team. Automatic Time Bill employee selection uses the Task's assignment and team.

Task

custrecord_nx_activity_task

Related CRM Task.

Supplies the service-work relationship used to retrieve activities for time processing. It doesn't reference a Project Task.

Latitude

custrecord_nx_activity_latitude

Available latitude captured with the event.

A numeric coordinate for the employee position available to FSM Mobile when the event is captured. The value can be absent.

Longitude

custrecord_nx_activity_longitude

Available longitude captured with the event.

A numeric coordinate paired with Latitude. Its presence doesn't establish the position's age or accuracy.

Key

custrecord_nx_activity_idempotency_key

Identifier used by the dedicated Activity synchronization process.

The synchronization process stores the request's idempotency identifier and searches Key for an earlier submission. This key is separate from the saved record's Internal ID and from user authentication.

Inactive (standard)

isinactive

Native record inactivity.

Separate from task completion, synchronization success, and time-processing results.

Dates and Duration with Processing Indicators

An Activity stores one event's date and clock time. It has no supplied duration field. Automatic time processing derives an elapsed interval from Start Task and Complete Task entries and stores the resulting hours on Time Bills. See FSM Service Time Tracking for calculation, selection, and processing limits.

Activity times can differ from the CRM Task's actual Field Service Start (custevent_nx_task_start) and Field Service End (custevent_nx_task_end) action timestamps. Activity times are also separate from the Task's planned Field Service dates and times.

The time-processing request is stored on the CRM Task in Field Service Log Activity Time (custevent_nx_time_log_activities). The Activity has no supplied pending, running, processed, or error-reference field. A saved Complete Task activity doesn't by itself establish that a Time Bill exists or that the Task has reached NetSuite Completed status.

Creation and Update Sources

Capture in FSM Mobile, synchronization to NetSuite, and subsequent time processing are separate stages.

Source	Effect on the record
FSM Mobile Start confirmation with automatic tracking enabled	Captures a Start Task activity with the current date, confirmed time, task time-zone reference, signed-in employee, CRM Task, and available employee coordinates.
FSM Mobile Update of the recorded start	Updates the selected Start Task activity's Time and Timezone. It doesn't capture another start location or replace the activity's Date.
FSM Mobile Complete confirmation with automatic tracking enabled	Captures a separate Complete Task activity with the current date, confirmed time, and the corresponding task, employee, time-zone, and coordinate data.
Dedicated FSM Activity synchronization	Creates or updates the saved Activity through the Activity service. Successful synchronization returns its NetSuite record identity.
Automatic time processing	Reads the Task's activities to calculate time for qualifying Time Bills. The process doesn't convert an Activity into a Time Bill or mark the Activity processed.

Source

Effect on the record

FSM Mobile Start confirmation with automatic tracking enabled

Captures a Start Task activity with the current date, confirmed time, task time-zone reference, signed-in employee, CRM Task, and available employee coordinates.

FSM Mobile Update of the recorded start

Updates the selected Start Task activity's Time and Timezone. It doesn't capture another start location or replace the activity's Date.

FSM Mobile Complete confirmation with automatic tracking enabled

Captures a separate Complete Task activity with the current date, confirmed time, and the corresponding task, employee, time-zone, and coordinate data.

Dedicated FSM Activity synchronization

Creates or updates the saved Activity through the Activity service. Successful synchronization returns its NetSuite record identity.

Automatic time processing

Reads the Task's activities to calculate time for qualifying Time Bills. The process doesn't convert an Activity into a Time Bill or mark the Activity processed.

Local capture doesn't confirm that NetSuite accepted the Activity. Task and Activity synchronization use separate requests. For the supported FSM Mobile capture procedure, see Tracking Field Service Time on Mobile.

Used by FSM Features

The Activity record stores event data. The following table explains how FSM Service Time Tracking uses that data.

Feature	How the record is used
FSM Service Time Tracking	Captures Start and Complete events and uses their dates and times as input to automatic Time Bills for CRM Tasks.

Feature

How the record is used

FSM Service Time Tracking

Captures Start and Complete events and uses their dates and times as input to automatic Time Bills for CRM Tasks.

Record Constraints and Data Requirements

The supplied record definition specifies no required custom fields or field defaults. FSM Mobile supplies values during capture. Form requirements and feature eligibility are separate from the record definition.

Automatic time processing requires a related CRM Task and recognized Start and Complete entries whose dates and times produce a positive interval. The Task Type's Service Time Item and other time-entry requirements belong to FSM Service Time Tracking. A saved Activity with incomplete data doesn't establish eligibility. Automatic tracking supports CRM Tasks only.

Adding another Activity Type doesn't by itself establish a new supported time-tracking event or calculation.

Retention and Related-Record Changes

Disabling automatic tracking leaves existing Activities in place. Time processing reads Activity entries without deleting the records. If the parent Task is deleted, the supplied Task relationship clears the Activity's Task reference without deleting the Activity.

Activity records and generated Time Bills remain separate data. Changing an Activity or reopening a Task doesn't reverse Time Bills already created. See FSM Service Time Tracking for the effects of later processing.