FSM Project Type Record
The Field Service Project Type record classifies projects in Field Service Management (FSM). Classifications include Billable, Warranty, and maintenance service categories. Projects and items refer to this FSM custom record through their Field Service Project Type fields.
FSM uses the classification in configured rules, project creation choices, and automatic project naming. The type identifies the service category. The project stores its customer, asset, dates, and service context. A type named PM Monthly doesn't define a monthly schedule by itself. For information about how configured rules use the project's type and data to plan service work, see FSM Program.
Record Information
The following table identifies the record and its references.
|
Property |
Value |
|---|---|
|
Record type |
FSM custom record |
|
Record name |
Field Service Project Type |
|
Record ID |
|
|
Record identity |
NetSuite internal ID, searched as |
|
Project reference field |
Field Service Project Type ( |
|
Supplied saved search |
Field Service Project Type Search ( |
Use the record's internal ID when configuration requires a project type ID. The type attribute in the FSM Project model maps to custentity_nx_project_type. This attribute is an alias, not another field on the type record.
The standard FSM Mobile event mappings also supply the linked project type as the project value for resource selection. This value identifies the project type rather than an individual project. For selection rules, see Selecting Resources.
FSM and Native NetSuite Project Type
NetSuite also has a native project type record. These classifications use separate records and fields.
|
Classification |
Record ID |
Project Field ID |
Purpose |
|---|---|---|---|
|
Field Service Project Type |
|
|
FSM service classification. |
|
Native NetSuite Project Type |
|
|
Separate NetSuite project classification. See Project Type. |
Selecting a native project type doesn't supply the Field Service Project Type required by an FSM rule or capability.
Project Forms
The supplied Field Service Project form (custform_nx_project) displays the FSM field as Type under Service Details and makes it required. It separately displays the native Project Type field. Both fields belong to the project, rather than to its Field Service Project Type record.
The supplied FSM project type field definition is optional and has no default selection. Forms created in an account can use different labels and requirements. Use the field ID to distinguish between the two classifications when labels are similar.
For the controls that select or create related projects, see FSM NetSuite View Configuration. These controls are separate from a custom form used to maintain the type's name and other record data.
Record Relationships
The referencing record stores the selected type. Multiple projects and items can reference the same field service project type.
|
Related Record |
Relationship and Field ID |
Purpose |
|---|---|---|
|
Project |
Project Field Service Project Type ( |
Classifies the project for FSM. Applies to project records, not project templates. |
|
Item |
Item Field Service Project Type ( |
Supplies the type for the standard process that automatically creates projects for new assets. |
|
Field Service Configuration |
Program, Billing Rule, and automatic notification rules can use project type IDs. These are configuration associations, not rule fields on the type record. |
Defines which classifications participate in configured behavior. See Configuring FSM Program, Configuring FSM Billing Rules, and FSM Notification Configuration. |
Cases and CRM tasks can reference a project through the native Company (company) field and use that project's type as context. The type record doesn't hold links to those individual service records. Selecting a type doesn't itself create an asset, case, or task relationship.
An account-specific custom link remains a separate relationship. Adding it doesn't automatically include the linked record in FSM Mobile, inheritance, history, reports, or synchronization.
FSM Fields
The supplied type record uses NetSuite identity, name, inactive, and name-translation data. It has no supplied FSM custom body fields.
|
Field or Data |
Field ID or Identifier |
Purpose |
Behavior |
|---|---|---|---|
|
Name |
|
Display name of the classification. |
A name can describe a service category or frequency. It doesn't store the rules that implement that meaning. |
|
Internal ID |
|
Identifies the individual type record in the account. |
Separate from the record type ID and the supplied instance script ID. Use the account's internal ID for the type record in settings that require it. |
|
Script ID |
|
Identifies a supplied record instance, such as |
FSM uses these script IDs to select supplied records for name-translation maintenance. These script IDs are not numeric project type IDs. |
|
Inactive |
|
Records whether the classification is inactive. |
Standard new-project choices exclude inactive types. This is not the project's status or a Program execution state. |
|
Name translations |
|
Holds localized names for the type. |
FSM maintains missing translated names for selected supplied types and existing locale entries. Account-created types don't automatically gain this maintenance. See FSM Localization and Translation. |
Supplied Project Types
FSM supplies the following active instances. The names shown are the supplied English names. Displayed names and available records can differ in an account.
|
Supplied Name |
Supplied Instance Script ID |
|---|---|
|
Billable |
|
|
Non Billable |
|
|
PM Annual |
|
|
PM 6 Monthly |
|
|
PM Quarterly |
|
|
PM Monthly |
|
|
PM Weekly |
|
|
Installation |
|
|
Warranty |
|
These names are classifications, not stored billing rules, warranty periods, or schedule intervals. The standard process for automatically creating projects for new assets uses the item's separate Project Duration value for the project period. Program uses configured rules and project dates. See Configuring FSM Automatic Project Creation for New Assets and Configuring FSM Program.
Creation and Update Sources
The following table describes sources that create or update type records.
|
Source |
Effect on the Type Record |
|---|---|
|
Supplied FSM data |
Provides the nine classification instances listed in the Supplied Project Types table. |
|
NetSuite record maintenance |
An authorized user can maintain the classification data. This is separate from creating a project that references the type. |
|
FSM Language processing |
Updates missing name translations on selected supplied instances when its language conditions apply. It doesn't define a service schedule or create projects. |
Used by FSM Features
The following table describes how FSM features use project types.
|
Feature |
Record Usage |
|---|---|
|
Uses the project's selected type to match project rules. Case rules can also use the resolved linked project type. |
|
|
Uses type choices when creating a project from a case, adding subprojects, or creating new service work through the enabled Mobile action. The Case and Mobile menu's standard new-project choices exclude types explicitly referenced by Program project rules. |
|
|
Reads the item's selected type and supplies it to the requested project. Warranty is one possible classification. |
|
|
Uses the selected classification in the standard project name. |
|
|
Can use the linked project type to select a CRM task's Billing Rule. A type named Billable doesn't select a rule by itself. |
|
|
Can use the related project type as a condition in automatic case, CRM task, and project task notification rules. |
|
|
Maintains translated names for selected supplied type instances. |
Record Constraints and Data Requirements
The supplied type record is not hierarchical. It doesn't hold the project's customer, asset, dates, Program rules, or processing requests. Those values and relationships belong to the project or the relevant configuration.
The project and item reference fields have no supplied default selection. Some FSM capabilities, including Project Program calculation, require a selected project type. The supplied Project form also requires a type. For other prerequisites, see the relevant feature and configuration topics.
An inactive type is excluded from standard new-project choices. Don't treat that flag as proof that Program processing has stopped for existing projects: Program's project-status classification and rule conditions are separate. The type record has no supplied running, completion, or error-reference field.