FSM Schedule Board Visibility and Editing Eligibility

This topic explains which records the Schedule Board loads and which records can be edited. For scheduling and assignment behavior in Field Service Management (FSM), see FSM Service Scheduling and Assignment.

Searches determine which records the Board loads. Panel filters and text searches then narrow the loaded information shown to the dispatcher. A panel filter cannot bring back a record excluded by the underlying search. Resource-panel filters affect the resource rows. Assigned-panel filters affect the events shown on those rows and in the assigned list. Unassigned-panel filters affect their own event list. Matching filter definitions across panels do not synchronize their selected values.

Assigned work is requested for the Board's date range and resource rows currently visible in its viewport. The unassigned-work panel requests work without an assignee, using its own date range. Resource filters and task filters serve different purposes: finding an employee does not establish that a task can be changed or assigned to that employee.

Changing the date, view, or visible resources requests work for that view. The Board also periodically requests updated data using its configured refresh interval.

Board Searches and Request Tags

The following table lists standard search selection rules before panel filtering.

Records	Standard Selection Logic
Employees	Active employees with a Field Service Region. In OneWorld accounts, the employee's subsidiary must be included in the dispatcher's view scope unless that scope is unrestricted.
CRM tasks	The primary assignee matches a requested resource, or a nonempty Field Service Task Team contains a requested resource. The task start date falls within the requested date range. In OneWorld accounts, the subsidiary rule uses the first available subsidiary from Case, Project, or Company. Tasks without any of those subsidiary values are also included.
Additional CRM tasks on related cases	A nested task search finds case IDs using those same resource, start-date, and subsidiary conditions. An outer `or` branch then loads other tasks on those cases, without repeating those conditions for each related task. These related tasks can fall outside the requested resource/date range. Being loaded does not mean the tasks are displayed or editable.
Project tasks, when enabled	A nested search finds project task IDs with an assignment to a requested resource. The task end date must be on or after the requested start. The task start date must be on or before the requested end. In OneWorld accounts, the project subsidiary must be in the view scope unless that scope is unrestricted. The outer search retrieves those IDs without restricting individual assignment rows, so the mapped resource list includes all assignments.
Employee non working days	The employee matches a requested resource and the non-working-day dates overlap the requested range. There is no separate `user.view` formula in this standard search.
Resource allocations, when enabled	The employee matches a requested resource and the allocation dates overlap the requested range. There is no separate `user.view` formula in this standard search.

Records

Standard Selection Logic

Employees

Active employees with a Field Service Region. In OneWorld accounts, the employee's subsidiary must be included in the dispatcher's view scope unless that scope is unrestricted.

CRM tasks

The primary assignee matches a requested resource, or a nonempty Field Service Task Team contains a requested resource. The task start date falls within the requested date range. In OneWorld accounts, the subsidiary rule uses the first available subsidiary from Case, Project, or Company. Tasks without any of those subsidiary values are also included.

Additional CRM tasks on related cases

A nested task search finds case IDs using those same resource, start-date, and subsidiary conditions. An outer or branch then loads other tasks on those cases, without repeating those conditions for each related task. These related tasks can fall outside the requested resource/date range. Being loaded does not mean the tasks are displayed or editable.

Project tasks, when enabled

A nested search finds project task IDs with an assignment to a requested resource. The task end date must be on or after the requested start. The task start date must be on or before the requested end. In OneWorld accounts, the project subsidiary must be in the view scope unless that scope is unrestricted. The outer search retrieves those IDs without restricting individual assignment rows, so the mapped resource list includes all assignments.

Employee non working days

The employee matches a requested resource and the non-working-day dates overlap the requested range. There is no separate user.view formula in this standard search.

Resource allocations, when enabled

The employee matches a requested resource and the allocation dates overlap the requested range. There is no separate user.view formula in this standard search.

The contextual searches depend on the requested resource set rather than repeating the employee subsidiary formula. Expanding that resource set can therefore also expand the contextual data retrieved. The Board's loaded data, displayed data, and editable data are separate results.

The following table describes the tags that the server resolves for each search request.

Tag	Meaning and Effect
`${ request.parameters.resource }`	Requested resource IDs. Assigned requests use visible resource rows. Unassigned requests are translated to the `@NONE@` value in NetSuite. The nonempty team condition prevents an empty team alone from matching.
`${ request.parameters.start }`, `${ request.parameters.end }`	The first and last requested dates. Assigned requests use Board dates. Unassigned requests use the unassigned panel's date range.
`${ user.view }`	Subsidiary IDs derived from the current user and role for viewing. A value of `0` means the FSM subsidiary view restriction is unrestricted. It is not a subsidiary ID.
`${ user.edit }`	Subsidiary IDs derived from the current user and role for editing. Standard employee and task `editable` mappings use this separately from view scope. A value of `0` means the FSM subsidiary editing restriction is unrestricted.

Tag

Meaning and Effect

${ request.parameters.resource }

Requested resource IDs. Assigned requests use visible resource rows. Unassigned requests are translated to the @NONE@ value in NetSuite. The nonempty team condition prevents an empty team alone from matching.

${ request.parameters.start }, ${ request.parameters.end }

The first and last requested dates. Assigned requests use Board dates. Unassigned requests use the unassigned panel's date range.

${ user.view }

Subsidiary IDs derived from the current user and role for viewing. A value of 0 means the FSM subsidiary view restriction is unrestricted. It is not a subsidiary ID.

${ user.edit }

Subsidiary IDs derived from the current user and role for editing. Standard employee and task editable mappings use this separately from view scope. A value of 0 means the FSM subsidiary editing restriction is unrestricted.

In a OneWorld account, FSM derives editing scope from the user's subsidiary plus the role's configured subsidiary list. Unless the role allows viewing all subsidiaries, view scope uses that restricted list. The Administrator role uses unrestricted scope. Outside OneWorld, the subsidiary conditions are omitted. These values do not replace NetSuite record permissions. A dispatcher can have a wider view scope than editing scope, so visible work can remain read-only.

The following table lists standard editing conditions.

Record or Target	Editing Conditions
CRM task	Must have a Not Started status and fall within the dispatcher's applicable subsidiary editing scope. In Progress and Completed tasks can be displayed but cannot be selected for scheduling changes.
Project task	Must be Not Started, use a Fixed Start constraint, and belong to a project that allows all resources for tasks. The project must also fall within the applicable subsidiary editing scope.
Employee receiving an assignment	Must be eligible within the applicable subsidiary editing scope. Project task assignments additionally require the employee's Project Resource setting.
Employee non working day or resource allocation block	Provides scheduling context and is read-only on the Board. It is not an editable service-task assignment.

Record or Target

Editing Conditions

CRM task

Must have a Not Started status and fall within the dispatcher's applicable subsidiary editing scope. In Progress and Completed tasks can be displayed but cannot be selected for scheduling changes.

Project task

Must be Not Started, use a Fixed Start constraint, and belong to a project that allows all resources for tasks. The project must also fall within the applicable subsidiary editing scope.

Employee receiving an assignment

Must be eligible within the applicable subsidiary editing scope. Project task assignments additionally require the employee's Project Resource setting.

Employee non working day or resource allocation block

Provides scheduling context and is read-only on the Board. It is not an editable service-task assignment.

These are the standard conditions. Account configuration can affect record selection and editing behavior. Enabling Board editing does not make every displayed task or employee eligible. For configuration risks and the controlled removal of CRM case expansion, see Search Filters and Panel Filters.

Board Searches and Request Tags

Related Topics