FSM Time Zone Record

In Field Service Management (FSM), a time zone record identifies a time zone used by service records. It is supplied reference data that connects a selected zone with its Olson identifier, numeric offset, and abbreviation.

A service record stores its time-zone selection separately from its service dates and clock times. Applicable FSM capabilities interpret those dates and times in the selected zone. The time zone record doesn't store an individual service location, schedule, or technician's work activity.

Record Information

Use these identifiers when working with searches, record references, and field mappings. Labels can vary by account or language.

Property	Value
Record type	FSM custom record
Supplied record name	Field Service Time Zone
Record Type ID	`customrecord_nx_time_zone`
Record identity	NetSuite Internal ID (`internalid`)
Display name	Name (`name`)

Property

Value

Record type

FSM custom record

Supplied record name

Field Service Time Zone

Record Type ID

customrecord_nx_time_zone

Record identity

NetSuite Internal ID (internalid)

Display name

Name (name)

The record type ID is used for both record access and searches. A service record's List/Record field stores a reference to a time zone record. That reference, the display name, and the Olson text are different values. Depending on the mapping, FSM can represent a selected zone as an Olson string or an object containing an ID and display label.

Record Relationships

The following supplied relationships are stored on service records rather than on time zone records. Each field selects one zone, and several records can select the same zone.

Related record	Relationship and field ID	Purpose
FSM Asset Record	Asset Time Zone (`custrecord_nx_asset_time_zone`) references the time zone record.	Identifies the asset's service-time context and can supply a zone to related work.
Project	Project Field Service Time Zone (`custentity_nx_time_zone`) references the time zone record.	Holds the project's service-time context.
FSM Case Record	Case Field Service Time Zone (`custevent_nx_time_zone`) references the time zone record.	Provides the context for the case's Field Service dates and clock times.
FSM CRM Task Record	CRM Task Field Service Time Zone (`custevent_nx_time_zone`) references the time zone record.	Provides the context for the planned Field Service schedule and applicable native date/time conversion.
Project Task	Project Task Field Service Time Zone (`custevent_nx_time_zone`) references the time zone record.	Holds the project task's service-time context. This relationship doesn't provide CRM task conversion behavior.
Field Service Activity	Activity Timezone (`custrecord_nx_activity_time_zone`) on `customrecord_nx_activity` references the time zone record.	Supplies the time-zone context for the activity's separately stored date and time. This is the custom service-activity record, distinct from a CRM task or project task.

Related record

Relationship and field ID

Purpose

FSM Asset Record

Asset Time Zone (custrecord_nx_asset_time_zone) references the time zone record.

Identifies the asset's service-time context and can supply a zone to related work.

Project

Project Field Service Time Zone (custentity_nx_time_zone) references the time zone record.

Holds the project's service-time context.

FSM Case Record

Case Field Service Time Zone (custevent_nx_time_zone) references the time zone record.

Provides the context for the case's Field Service dates and clock times.

FSM CRM Task Record

CRM Task Field Service Time Zone (custevent_nx_time_zone) references the time zone record.

Provides the context for the planned Field Service schedule and applicable native date/time conversion.

Project Task

Project Task Field Service Time Zone (custevent_nx_time_zone) references the time zone record.

Holds the project task's service-time context. This relationship doesn't provide CRM task conversion behavior.

Field Service Activity

Activity Timezone (custrecord_nx_activity_time_zone) on customrecord_nx_activity references the time zone record.

Supplies the time-zone context for the activity's separately stored date and time. This is the custom service-activity record, distinct from a CRM task or project task.

Parent and child service records can hold different zones. A stored selection doesn't establish that a geographic lookup occurred or that the record remains synchronized with the zone on a related source record. For sourcing and later changes, see FSM Service Time Zone Sourcing and Synchronization.

The current NetSuite user's time-zone preference and the Schedule Board's viewing time zone are separate contexts. Neither is an additional relationship field on the time zone record.

An account-created field can also reference this record type. That link alone doesn't add the custom record to FSM sourcing, date and time conversion, FSM Mobile synchronization, history, or reports.

FSM Fields

The supplied custom fields store reference values. They are not per-record conversion results or processing indicators.

Field	Field ID	Purpose	Important values or behavior
Name (standard)	`name`	Display name of the zone.	Supplied names combine a GMT offset with a regional description. Identify an individual time zone record by its internal ID rather than its display name.
Olson	`custrecord_nx_time_zone_olson`	Named time-zone identifier used in time-zone interpretation and search formulas.	Stored text, such as `Australia/Sydney`. The identifier represents a zone rather than a service address, coordinates, or the offset for an individual date.
Offset	`custrecord_nx_time_zone_offset`	Numeric reference offset from GMT, expressed in hours.	Stored as a decimal number that can include fractional hours. It is not a date-specific daylight-saving calculation and is not interchangeable with a named zone.
Abbreviation	`custrecord_nx_time_zone_abbreviation`	Short display text for the zone.	Stored text used by FSM labels. An abbreviation is not a unique record identifier or a conversion rule.

Field

Field ID

Purpose

Important values or behavior

Name (standard)

name

Display name of the zone.

Supplied names combine a GMT offset with a regional description. Identify an individual time zone record by its internal ID rather than its display name.

Olson

custrecord_nx_time_zone_olson

Named time-zone identifier used in time-zone interpretation and search formulas.

Stored text, such as Australia/Sydney. The identifier represents a zone rather than a service address, coordinates, or the offset for an individual date.

Offset

custrecord_nx_time_zone_offset

Numeric reference offset from GMT, expressed in hours.

Stored as a decimal number that can include fractional hours. It is not a date-specific daylight-saving calculation and is not interchangeable with a named zone.

Abbreviation

custrecord_nx_time_zone_abbreviation

Short display text for the zone.

Stored text used by FSM labels. An abbreviation is not a unique record identifier or a conversion rule.

For example, the supplied Sydney entry contains Olson Australia/Sydney, Offset 10, and Abbreviation AEST. These stored catalog values don't establish the UTC offset or abbreviation for every service date. Use the date and named zone for date-specific interpretation rather than calculating from the stored Offset alone.

Searches can join through a service record's time-zone field to read the reference data. For example, a CRM task search can use {custevent_nx_time_zone.custrecord_nx_time_zone_olson} to obtain its selected zone's Olson text. This expression retrieves the Olson value without converting a date or time. For mapping syntax, see FSM Record Model Configuration.

Creation and Update Sources

FSM supplies the Time Zone catalog as product reference data. Geographic lookup selects a supported zone for an asset without creating a time zone record for the asset's coordinates. Related-record sourcing and user-preference fallback update selections on the service records.

Date/time synchronization updates the applicable service-record values. It doesn't update the catalog's Offset or Abbreviation for each service date. The detailed sourcing and synchronization rules belong to FSM Service Time Zone Sourcing and Synchronization.

Used by FSM Features

These capabilities use the zone identity or a service record's selection. For details about each feature's behavior and requirements, see the linked feature topic.

Feature	How the record is used
FSM Service Time Zone Sourcing and Synchronization	Supplies supported time-zone identity for asset lookup, related-record sourcing, and applicable case/CRM task date/time conversion.
FSM Service Scheduling and Assignment	Provides service-time context for task scheduling. The Board's viewing zone is a separate choice.
FSM Service Time Tracking	Provides time-zone context for stored service-activity dates and times. Selecting a zone doesn't capture work or create a time bill.

Feature

How the record is used

FSM Service Time Zone Sourcing and Synchronization

Supplies supported time-zone identity for asset lookup, related-record sourcing, and applicable case/CRM task date/time conversion.

FSM Service Scheduling and Assignment

Provides service-time context for task scheduling. The Board's viewing zone is a separate choice.

FSM Service Time Tracking

Provides time-zone context for stored service-activity dates and times. Selecting a zone doesn't capture work or create a time bill.

Record Constraints and Data Requirements

The supplied record definition declares no initial values for Olson, Offset, or Abbreviation and doesn't mark these fields as required. The supplied catalog populates these fields. These settings don't establish whether FSM can use an incomplete or newly created time zone record.

FSM uses a supported time-zone catalog. Adding another custom record or changing an existing record's Olson, Offset, or Abbreviation doesn't by itself add support for a new zone. Preserve the supported identity and mapping described in Configuring FSM Service Time Zone Sourcing and Synchronization.

Service-record forms can present the time-zone selection under different labels. Form requirements and feature prerequisites apply to service records without changing the meaning of the catalog fields. See the related record topics for their form guidance.