FSM Employee Non-Working Day Record
In Field Service Management (FSM), an Employee Non-Working Day record identifies an employee's unavailable period. Examples include leave or another absence. It identifies the employee and the first and last dates of that period.
FSM uses this custom record to display employee-specific unavailability on the Schedule Board. A shared work-calendar exception uses a separate Non-Working Day record and applies through the calendar associated with an employee.
Record Information
The following table summarizes the record's identifiers and Schedule Board mapping.
|
Property |
Value |
|---|---|
|
Record type |
FSM custom record |
|
Supplied record name |
Field Service Employee Non Working Day |
|
Record ID |
|
|
Record identity |
NetSuite Internal ID ( |
|
Display name |
Name ( |
|
Schedule Board definition |
|
nonworkingday is the Schedule Board definition name, not a NetSuite record type. The standard Schedule Board identifies each displayed block as nonworkingday-<internal ID>. Use the underlying NetSuite internal ID when identifying the saved record.
Field labels can vary by account. For field IDs that identify the stored data, see FSM Fields.
Record Relationships
The following table describes the employee relationship.
|
Related Record |
Relationship and Field ID |
Purpose |
|---|---|---|
|
Employee ( |
The Employee field ( |
Identifies the person whose unavailable dates are recorded. One employee can have several non-working-day records. |
In the supplied record definition, these child records appear on the Field Service subtab of the employee record. The dates belong to the Employee Non-Working Day record; they are separate from the employee's calendar association and Task assignments.
The shared FSM Non-Working Day Record (customrecord_nx_non_working_day) stores one Date (custrecord_nx_work_calendar_date) and a Work Calendar reference (custrecord_nx_work_calendar). It supplies an exception to an FSM Work Calendar and has no Employee or date-range fields. Native NetSuite Work Calendar exceptions are separate.
FSM Fields
The following table describes the record's fields and date behavior.
|
Field |
Field ID |
Purpose |
Behavior |
|---|---|---|---|
|
Name (standard) |
|
Describes the unavailable period. |
Used as the standard Schedule Board block's label and title. |
|
Employee |
|
Identifies the affected employee. |
Stored List/Record field. Required in the supplied record definition. |
|
Start Date |
|
First unavailable date. |
Stored Date field. Required in the supplied record definition. The standard Schedule Board includes the whole start date. |
|
End Date |
|
Last unavailable date. |
Stored Date field. Required in the supplied record definition. The standard Schedule Board includes the whole end date. |
The dates represent calendar days, not a number of hours or a percentage of resource capacity. The record has no separate start-time, end-time, duration, or allocation-units field. The supplied definitions don't set an initial Employee, Start Date, or End Date value.
For a one-day absence, Start Date and End Date identify the same date. The date range includes the start date, end date, and every date between.
Creation and Update Sources
Maintain the record through NetSuite record entry using an authorized role. The Employee parent relationship provides the connection to the employee's record.
The standard Schedule Board displays these records as contextual blocks. Dragging and saving tasks doesn't change the Employee, Name, or date fields on these records. Schedule Board configuration controls which records appear and how each block is displayed. For more information, see FSM Schedule Board Searches and Editing Constraints.
Used by FSM Features
The following table identifies the FSM feature that uses this record.
|
Feature |
Record Use |
|---|---|
|
Supplies read-only unavailable blocks for the requested employees when the stored date range overlaps the Board's requested dates. |
The standard Schedule Board displays the period from the beginning of Start Date to the end of End Date. Displaying unavailable time helps dispatchers assess an assignment. The display doesn't prevent overlapping work or stop a Task from being assigned during that period. Calendar shading and Project Task work calculations use their own calendar information.
Record Constraints and Data Requirements
Employee, Start Date, and End Date are required by the supplied custom-field definitions. Enter a date range with End Date on or after Start Date so that it represents the intended unavailable period.
The record represents whole-day unavailability. It doesn't provide fields for a partial-day absence or a recurring absence pattern. Board visibility additionally depends on the requested employees and dates, account configuration, and active Schedule Board filters.