FSM Employee Record

An employee identifies a person who performs or manages service work in Field Service Management (FSM). FSM uses the standard NetSuite employee record and adds fields for FSM Mobile access, operating region, skills, availability, inventory locations, language, and location coordinates.

The employee record identifies the person. The Schedule Board configuration selects and displays that person as a resource. An FSM Mobile resource instead defines a page or supporting data in FSM Mobile.

Record Information

Use the record and field IDs to distinguish saved data from account-specific labels and display values.

Property

Value

Record type

Standard NetSuite

Record name

Employee

Record ID

employee

Record identity

Internal ID (internalid) identifies the saved record. Employee ID (entityid) is the displayed employee identifier.

FSM record model

models/employee

Schedule Board resource definition

routes/scheduler.resource.employee

FSM Mobile user definition

routes/mobile.user.employee

models/employee, the Schedule Board resource definition, and the FSM Mobile user definition use the same employee data but have separate mappings and purposes. Changing one definition doesn't automatically change the other two. For the native record, see Employee.

Forms

FSM adds the Field Service subtab to employee records to hold the technician's FSM data. An employee form created for your account can change field visibility, labels, and form requirements. See Field Service Subtabs on Employee and Customer Records.

The preferred employee form in NetSuite and role-specific form settings determine the default UI presentation. A role's preferred form takes precedence over the general form preference. Where a custom entry form provides Store Form with Record, that setting retains the form used for records created with it. Form options vary by form type. See Defining Preferred Forms and Custom Entry Form Properties.

The standard FSM Mobile user definition reads mapped employee fields directly, rather than generating the technician's data from an employee entry form. Choosing or storing an employee form therefore doesn't determine the technician's tabs in FSM Mobile. For more information about form-generated FSM Mobile elements and their overrides, see Form Properties.

Record Relationships

Employee references identify the person. Assignment, activity, time, and inventory records store their own links to that person.

Related Record

Relationship and Field ID

Purpose

Role

Employee Roles sublist, roles.selectedrole, references assigned roles. Employee searches expose role.

Supplies the roles available to a NetSuite user. FSM access controls on a role are separate from fields on the employee.

Subsidiary

Employee subsidiary references one subsidiary in OneWorld.

Provides the technician's subsidiary context for applicable visibility, assignment, and inventory rules.

Field Service Skill

Employee Field Service Skill (custentity_nx_skill) selects multiple customrecord_nx_skill records.

Records skills for resource information and filtering. Several employees can reference the same skill.

Field Service Work Calendar

Employee custentity_nx_work_calendar references customrecord_nx_work_calendar.

Associates the employee with the FSM calendar. Several employees can share one calendar.

Native Work Calendar

Employee workcalendar references a NetSuite work calendar.

Provides native Project Management availability. Separate from the FSM calendar relationship.

Employee Non Working Day

The non-working-day record (customrecord_nx_employee_non_working_day) stores Employee in custrecord_nx_emp_avail_emp.

Records employee-specific non-working dates. An employee can have multiple entries. These are separate from shared calendar exceptions.

Inventory Location

Employee custentity_nx_location and custentity_nx_warehouse each reference a NetSuite location.

Identify the employee's stock location and the warehouse used as an initial transfer choice. These are separate links.

Field Service Language

Employee custentity_fsm_language references customrecord_fsm_language.

Supplies the employee's FSM language selection.

CRM Task

The task stores its primary employee in assigned and additional employees in Field Service Task Team (custevent_nx_task_team).

Connects the visit to its technician and team. Several tasks can reference the same employee.

Project Task

The project task stores employees in its native resource-assignment sublist, assignee.resource.

Connects project work to assigned resources. Separate from CRM task primary and team fields.

Case

The case record stores the responsible employee in assigned.

Identifies responsibility for the service request. It doesn't assign every child task.

Service sign-off

Case, CRM task, and project task Field Service Sign Off Technician (custevent_nx_signoff_technician) references the employee.

Identifies the technician recorded in sign-off data, separately from the work assignment.

Field Service Activity

Activity Employee (custrecord_nx_activity_employee) on customrecord_nx_activity references the employee.

Identifies the person associated with the captured activity.

Time Bill

Native time bill employee references the employee.

Attributes recorded service time to the employee.

Consumable

Consumable Employee (custrecord_nx_consemployee) on customrecord_nx_consumable references the employee.

Identifies the employee associated with the recorded item usage.

The primary assignee, team member, case assignee, and activity employee are distinct relationships. The person recording an activity is not necessarily the only person receiving an automatically generated time bill. See FSM Service Time Tracking.

Adding an account-specific employee link to another record doesn't automatically include that record in FSM Mobile, scheduling, service history, or synchronization. The applicable feature and configuration determine how the relationship is used.

FSM Fields

The following tables describe FSM fields and the native NetSuite fields used with FSM. Field availability and labels can vary by form, role, and enabled NetSuite features.

Identity and Access

The employee's FSM Mobile designation, native NetSuite access, and role permissions are separate controls.

Field

Field ID

Purpose

Values and Behavior

Employee ID, First Name, Middle Name, and Last Name

entityid, firstname, middlename, lastname

Identify the employee to users.

The standard Board and FSM Mobile labels use the available name, falling back to Employee ID. The saved Internal ID remains the record identity.

Email

email

Identifies the employee for applicable FSM Mobile sign-in and login-link operations.

Also supplies the recipient for the standard employee FSM Mobile login email.

Inactive

isinactive

Indicates whether the employee is inactive.

Standard Board resource selection and FSM Mobile user lookup exclude inactive employees.

Give Access

giveaccess

Controls native access to NetSuite.

Distinct from Field Service Mobile User and from task assignment.

Field Service Mobile User

custentity_nx_mobile_user

Designates the employee as an FSM Mobile user.

The Field Service Mobile User box is cleared by default. The designation participates in FSM Mobile-user and license assessment. It doesn't grant every NetSuite record permission or make all tasks available.

Field Service Password

custentity_nx_password

Stores the password used by the FSM Mobile-only email/password authentication path.

Separate from native NetSuite Password (password). The save rule requires a Field Service Password value when the Field Service Mobile User box is checked and the Give Access box is cleared.

Subsidiary

subsidiary

Identifies the employee's native NetSuite subsidiary.

Used where OneWorld subsidiary conditions apply.

Field Service Mobile (custrecord_nx_mobile) and Field Service Scheduler (custrecord_nx_scheduler) are fields on the role record. They are not employee checkboxes. Field Service Mobile contributes to eligibility to administer FSM Mobile, and Field Service Scheduler contributes to eligibility to edit the Schedule Board. Neither replaces NetSuite permissions. For Board access and editing controls, see Configuring FSM Service Scheduling and Assignment.

The employee form's Mobile Login and Email Mobile Login buttons are actions rather than stored employee fields. Their visibility and notification settings are covered in Employee Mobile Login Button.

Skills and Availability

These fields describe the technician and the availability information used by scheduling.

Field

Field ID

Purpose

Values and Behavior

Field Service Region

custentity_nx_region

Operational region from customlist_nx_region.

The standard Schedule Board includes active employees with a value in Field Service Region and uses that value for grouping and filtering. The selection condition applies to the Schedule Board and is not a save requirement for every employee record.

Field Service Skill

custentity_nx_skill

Multiple references to Field Service Skill records.

Supports resource information and skill filtering. A selected skill doesn't establish automatic skill enforcement for every assignment.

Field Service Work Calendar

custentity_nx_work_calendar

Employee's FSM calendar association.

The standard Board uses this association when Project Management is disabled.

Work Calendar (native)

workcalendar

Employee's NetSuite work calendar.

The standard Board uses this association when Project Management is enabled. For native calendar assignment, see Assigning a Resource Work Calendar.

Project Resource (native)

isjobresource

Identifies an employee eligible as a native project resource.

Relevant to project task assignment. It is not required for every FSM employee or CRM task assignment.

Support Rep (native)

issupportrep

Identifies an employee available to native case assignment.

Separate from task assignment and FSM Mobile access.

Mobile Phone, Image

mobilephone, image

Contact number and employee image used in resource presentation.

Don't determine scheduling eligibility.

Job Title, Department, and Notes

title, department, comments

Additional employee information used in standard Board resource mappings.

Job Title and the available Department or Subsidiary supply presentation context. Notes contribute to resource-search details. Mapping a value doesn't automatically display it as a separate field.

For calendar selection, skills, and assignment conditions, see FSM Service Scheduling and Assignment. Availability information doesn't itself select a technician or guarantee that assignments avoid overlaps.

Inventory and Cost with Language Settings

The following values supply inventory, costing, and language context. They don't represent the service address of a task or asset.

Field

Field ID

Purpose

Values and Behavior

Field Service Employee Location

custentity_nx_location

NetSuite inventory location assigned to the employee, such as a van.

Supplies the employee location used for stock usage and transfers. It is separate from native Employee Location (location) and geographic coordinates.

Field Service Employee Warehouse

custentity_nx_warehouse

NetSuite location used as the initial other-location choice for stock transfers.

Can be the source for an Order or the destination for a Return if the warehouse is among the allowed choices. It doesn't restrict all transfers to that warehouse.

Field Service Labour Cost

custentity_nx_labor_cost

Employee's internal labor-cost rate.

Standard sourcing supplies the employee's rate to the Field Service Time Cost field (custcol_nx_time_cost) on time bills. Labor posting uses the saved hourly cost. Changing the employee's rate doesn't recalculate costs already saved on time bills.

Labor Cost (native)

laborcost

The native employee labor-cost field in NetSuite.

Separate from Field Service Labour Cost. Standard FSM Time Cost sourcing references the custom FSM field.

Field Service Language

custentity_fsm_language

Employee's FSM language choice.

With Multi-Language enabled, participates in FSM Mobile labels, employee notifications, and Enhanced Technician Notes prompt selection. Blank uses the applicable fallback. Browser date and number formatting remains separate.

Employee stock locations should use the employee's subsidiary where subsidiaries apply. Both supplied inventory-location selectors restrict choices to locations with inventory available. Transfer choices and stock eligibility have additional conditions. See FSM Mobile Stock Transfers and Managing Warehouse and Van Locations for Field Service Management.

For saved hourly cost and posting, see FSM Project Labor Cost Posting. For language sources and fallbacks, see FSM Localization and Translation.

Location and Notification Data

Coordinates describe the employee position available to FSM. Notification data describes outstanding requests, rather than delivery or execution status.

Field

Field ID

Meaning and Values

Field Service Latitude

custentity_nx_latitude

Saved employee latitude, used with Longitude for position display and navigation.

Field Service Longitude

custentity_nx_longitude

Saved employee longitude, used with Latitude for the same purposes.

Field Service Geolocation

custentity_nx_geo_location

Additional stored geolocation text. The standard Board and FSM Mobile position mappings use the separate Latitude and Longitude fields.

Field Service Pending Notifications

custentity_nx_notification_pending

Stores notification requests awaiting corresponding Field Service Notification records. Processing clears transferred requests. An empty field doesn't establish that an email was sent or delivered.

With device location tracking enabled, FSM Mobile can save received device coordinates to the signed-in employee's Latitude and Longitude. A displayed or saved position alone doesn't establish when the device last supplied coordinates. See FSM Maps and Location Tracking.

Pending Notifications is FSM-maintained request data, not a script-running flag. The separate notification and message records provide later processing results. See FSM Service Reports and Notifications.

Creation and Update Sources

Different operations maintain the employee and the related work records separately.

Source

Record Effect

NetSuite employee entry or authorized integration

Creates or updates the native employee and available FSM fields, subject to native record, permission, and applicable form or script validation.

Employee FSM Mobile-access form and save handling

Maintains the applicable FSM Mobile-only password and validates the Mobile User/Give Access combination.

FSM Mobile device location updates

Can synchronize received Latitude and Longitude to the signed-in employee. Capturing coordinates on the device doesn't confirm that NetSuite saved the coordinates.

Employee login-email action and notification processing

Adds and transfers pending notification requests. Creates separate notification and message records through processing.

Schedule Board assignment

Updates the task's assignment and schedule. It doesn't update the employee's skills or calendar.

FSM employee form handling uses Field Service User Event (customscript_nx_userevent, customdeploy_nx_employee_userevent) and Field Service Client (customscript_nx_client, customdeploy_nx_employee_client). Employee login notifications use Field Service Scheduled : Notification (customdeploy_nx_notification). Script execution and deployment controls belong in FSM Script Reference.

Used by FSM Features

These features use employee data or records linked to the employee.

Feature

Record Use

FSM Service Scheduling and Assignment

Supplies resource identity, subsidiary context, skills, and calendar associations.

FSM Maps and Location Tracking

Supplies employee positions and receives device-coordinate updates.

FSM Mobile Stock Transfers

Supplies employee stock location, warehouse, and subsidiary context.

FSM Service Time Tracking

Attributes activities and time bills to employees. Task assignment and team membership determine which employees receive automatically generated time bills.

FSM Project Labor Cost Posting

Uses the employee as the standard source of saved time bill cost.

FSM Localization and Translation

Uses the employee's Field Service Language for applicable FSM Mobile labels and employee notifications.

FSM Enhanced Technician Notes

Uses the effective employee language when selecting a related prompt.

FSM Service Reports and Notifications

Uses employee identity for senders and the employee FSM Mobile login email.

Record Constraints and Data Requirements

The FSM custom-field definitions don't make these fields required for every employee record. The Field Service Mobile User box is cleared by default, and the employee model supplies no additional initial values. Native NetSuite requirements and account-specific form, role, and validation rules still apply.

A person can be a valid employee without being an FSM Mobile user, a Board resource, a Project Resource, or a Support Rep. Each use has its own conditions. A task assignment alone doesn't establish that the employee can sign in or that the assigned work is available in FSM Mobile.

The FSM Mobile-only password requirement applies when Field Service Mobile User is checked and Give Access is clear. When Give Access is checked, the email/password path validates NetSuite credentials instead. These authentication conditions are separate from business eligibility for assignment.

Additional Information

Related Topics

General Notices