FSM Case Type Record

In Field Service Management (FSM), a case type classifies the service work represented by a case, such as Install, Maintenance, Repair, or Uninstall. FSM uses this classification in configured rules and in service-work displays.

Field Service Case Type is an FSM custom record. A case stores its selection in Field Service Case Type (custevent_nx_case_type). A type's name describes the work but doesn't define a service schedule, create tasks, or record the work performed.

Record Information

The following table identifies the case type record and its associated fields and search.

Property	Value
Record type	FSM custom record
Record name	Field Service Case Type
Record ID	`customrecord_nx_case_type`
Record identity	NetSuite Internal ID (`internalid`)
Display name	Name (`name`)
Referencing case field	Field Service Case Type (`custevent_nx_case_type`), labeled Case Type on the supplied FSM Case form.
Supplied search	Field Service Case Type Search (`customsearch_nx_case_type_search`)

Property

Value

Record type

FSM custom record

Record name

Field Service Case Type

Record ID

customrecord_nx_case_type

Record identity

NetSuite Internal ID (internalid)

Display name

Name (name)

Referencing case field

Field Service Case Type (custevent_nx_case_type), labeled Case Type on the supplied FSM Case form.

Supplied search

Field Service Case Type Search (customsearch_nx_case_type_search)

When a configuration requires a Case Type ID, use the record internal ID of the case type entry in your account. The entry's display name and instance script ID are separate identifiers. Example IDs in configuration topics are illustrative.

FSM and Native Support Case Types

NetSuite also has native Support Case Types for classifying customer support issues. The following fields identify different classifications, even when a form labels both of them Type or Case Type.

Classification	Case Field	Referenced Record
FSM service classification	`custevent_nx_case_type`	Field Service Case Type (`customrecord_nx_case_type`)
Native support classification	`category`	NetSuite Support Case Type (`SupportCaseType` in SOAP web services).

Classification

Case Field

Referenced Record

FSM service classification

custevent_nx_case_type

Field Service Case Type (customrecord_nx_case_type)

Native support classification

category

NetSuite Support Case Type (SupportCaseType in SOAP web services).

Selecting a native support Type doesn't supply the FSM classification. For native setup and API details, see Creating Case Types and Support Case Type.

Forms and Selection

The supplied FSM Case form (custform_nx_case) requires a Case Type selection. The underlying custom case field definition doesn't require a value or provide a default selection. Account-created case forms can present the field differently. For case form guidance, see FSM Case Record.

The standard FSM Mobile Add New Task form also requires a Case Type when that menu action is enabled. It loads option IDs and names from the case type records. This selection supplies the classification for the new case. It doesn't create or edit the case type record. The FSM Mobile control has its own configuration rather than using the case type record's NetSuite entry form. For more information about related service work and its configuration, see FSM Related Service Work and Configuring FSM Related Service Work.

Record Relationships

The following table describes the case type's relationships with other records and configuration.

Related Record or Data	Relationship and Field ID	Purpose
Case	The `custevent_nx_case_type` field on a case references `customrecord_nx_case_type`. Several cases can reference the same type.	Classifies each service request or occurrence. The relationship is stored on the case.
CRM task	A task references a case through native `supportcase`; task searches use `case`. The `case.custevent_nx_case_type` search join reads the parent case's classification.	Makes the parent case type available to task displays and applicable rules. It is separate from the task's own Field Service Task Type (`custevent_nx_task_type`).
Program rules	Configuration contains case type IDs as project-rule outputs or case-rule conditions.	Associates a classification with configured work generation. These are configuration references, not rule fields on the case type record.
Recurring cases	Each case occurrence retains its own `custevent_nx_case_type` reference. The case's separate `custevent_nx_recurrence` field identifies its series.	Preserves the service classification across occurrences without storing a recurrence pattern on the case type.

Related Record or Data

Relationship and Field ID

Purpose

Case

The custevent_nx_case_type field on a case references customrecord_nx_case_type. Several cases can reference the same type.

Classifies each service request or occurrence. The relationship is stored on the case.

CRM task

A task references a case through native supportcase; task searches use case. The case.custevent_nx_case_type search join reads the parent case's classification.

Makes the parent case type available to task displays and applicable rules. It is separate from the task's own Field Service Task Type (custevent_nx_task_type).

Program rules

Configuration contains case type IDs as project-rule outputs or case-rule conditions.

Associates a classification with configured work generation. These are configuration references, not rule fields on the case type record.

Recurring cases

Each case occurrence retains its own custevent_nx_case_type reference. The case's separate custevent_nx_recurrence field identifies its series.

Preserves the service classification across occurrences without storing a recurrence pattern on the case type.

A case type named Repair is separate from a Repair record that captures service results. Similarly, a Maintenance classification doesn't itself hold a maintenance checklist.

Custom links to a case type in your account don't automatically add inheritance, presentation in FSM Mobile, service-history reporting, or synchronization. Those uses require their own supported configuration or processing.

FSM Fields

Case types use the native custom-record identity and name fields in the following table. The supplied FSM case type definition adds no custom body fields.

Field	Field ID	Purpose	Values and Behavior
Name	`name`	Display name of the classification.	Supplied names are Install, Maintenance, Repair, and Uninstall. A name doesn't determine which rules apply.
Internal ID	`internalid`	Identifies the saved type within the account.	Used by case references, searches, and ID-based configuration. It is separate from a case number.
Script ID	`scriptid`	Identifies the custom-record instance independently of its display name.	FSM translation maintenance identifies the four supplied instances by the instance script IDs in the Supplied values table. This is separate from the record type ID.
Inactive	`isinactive`	Records the type's inactive state.	It is not a case status or a processing indicator. Inactivating a type doesn't delete its existing cases or end their recurrence series.
Translated name	`translations.locale`, `translations.label`	Locale and translated label entries in the native translations sublist.	FSM Language processing maintains names for selected supplied instances. It doesn't translate every account-created case type automatically.

Field

Field ID

Purpose

Values and Behavior

Name

name

Display name of the classification.

Supplied names are Install, Maintenance, Repair, and Uninstall. A name doesn't determine which rules apply.

Internal ID

internalid

Identifies the saved type within the account.

Used by case references, searches, and ID-based configuration. It is separate from a case number.

Script ID

scriptid

Identifies the custom-record instance independently of its display name.

FSM translation maintenance identifies the four supplied instances by the instance script IDs in the Supplied values table. This is separate from the record type ID.

Inactive

isinactive

Records the type's inactive state.

It is not a case status or a processing indicator. Inactivating a type doesn't delete its existing cases or end their recurrence series.

Translated name

translations.locale, translations.label

Locale and translated label entries in the native translations sublist.

FSM Language processing maintains names for selected supplied instances. It doesn't translate every account-created case type automatically.

Supplied Values

The supplied record definition includes four active instances. Their internal IDs are assigned in the account.

Supplied Name	Instance Script ID
Install	`val_nx_case_type_install`
Maintenance	`val_nx_case_type_maintenance`
Repair	`val_nx_case_type_repair`
Uninstall	`val_nx_case_type_uninstall`

Supplied Name

Instance Script ID

Install

val_nx_case_type_install

Maintenance

val_nx_case_type_maintenance

Repair

val_nx_case_type_repair

Uninstall

val_nx_case_type_uninstall

Name translation is enabled for this record type. For the scope and conditions of translated-name maintenance, see FSM Localization and Translation.

The case model uses the attribute type for custevent_nx_case_type. The standard FSM Mobile CRM task event maps its parent case type to case. The Schedule Board maps the same value to casetype. These are mapped data names, not additional fields on the case type record. See FSM Case Model Reference and Shared Rule Matching for the relevant mapping and rule contexts.

Creation and Update Sources

The following table describes how case type records are created and updated.

Source	Record Effect
FSM installation	Supplies the four named case type instances.
Authorized NetSuite entry	Creates or maintains case type reference data for the account. Selecting a type on a case references that existing data.
FSM Language processing	Updates translated names on selected supplied instances when Multi-Language and the applicable translation conditions are met.

Source

Record Effect

FSM installation

Supplies the four named case type instances.

Authorized NetSuite entry

Creates or maintains case type reference data for the account. Selecting a type on a case references that existing data.

FSM Language processing

Updates translated names on selected supplied instances when Multi-Language and the applicable translation conditions are met.

FSM Program, recurrence processing, and service work creation in FSM Mobile set or copy the case's reference to a type. They don't create a case type for each service occurrence. Case types have no supplied pending-work, running, completion, or error-reference fields.

Used by FSM Features

The following table describes how FSM features use case types.

Feature or Capability	Case Type Use
FSM Program	Project rules specify the types of cases to create. Case rules can select by case type to generate child tasks. Existing cases participate in matching by type and chronological order.
FSM Case and Task Recurrence	The standard set of copied case fields includes the FSM case type reference. The recurrence pattern belongs to the series, not to the type. Child tasks require separate Program rules.
FSM Related Service Work	The optional Add New Task action in FSM Mobile selects the type for its new case.
Resource selection in FSM Mobile	The mapped parent case type can participate in configured resource-selection rules. A type alone doesn't guarantee a tab or job is visible. See Selecting Resources.
Schedule Board presentation	The parent case type supplies a color-group value for CRM tasks and can support configured event-panel filters. It doesn't classify employee resource rows. See FSM Schedule Board Configuration.
FSM Automatic Record Naming	When an FSM case type is selected, case naming follows the standard naming conditions. The case type name forms part of the default case title.
FSM Localization and Translation	Maintains translated names for the selected supplied case type instances.

Feature or Capability

Case Type Use

FSM Program

Project rules specify the types of cases to create. Case rules can select by case type to generate child tasks. Existing cases participate in matching by type and chronological order.

FSM Case and Task Recurrence

The standard set of copied case fields includes the FSM case type reference. The recurrence pattern belongs to the series, not to the type. Child tasks require separate Program rules.

FSM Related Service Work

The optional Add New Task action in FSM Mobile selects the type for its new case.

Resource selection in FSM Mobile

The mapped parent case type can participate in configured resource-selection rules. A type alone doesn't guarantee a tab or job is visible. See Selecting Resources.

Schedule Board presentation

The parent case type supplies a color-group value for CRM tasks and can support configured event-panel filters. It doesn't classify employee resource rows. See FSM Schedule Board Configuration.

FSM Automatic Record Naming

When an FSM case type is selected, case naming follows the standard naming conditions. The case type name forms part of the default case title.

FSM Localization and Translation

Maintains translated names for the selected supplied case type instances.

Additional case functions use the populated classification alongside their own prerequisites. See FSM Case Record for the associated fields and feature references. Selecting a type doesn't enable every FSM capability.

Record Constraints and Data Requirements

Case types are a flat classification: the supplied record type is not hierarchical. They don't store a parent type, service interval, task template, billing rule, or recurrence definition.

Access to case type records is governed by the custom record type's permissions. Availability through an FSM selection or display doesn't grant permission to maintain that reference data.

Use the intended account's type IDs when configuring behavior. Selecting a case type doesn't confirm that Program rules match, recurrence is enabled, or service records have been generated. For the requirements, see the applicable feature and configuration topics linked in this topic.