FSM Resource Allocation Record

A resource allocation reserves a resource's time for a project over a date range. It can also identify a particular project task. Field Service Management (FSM) uses this standard NetSuite record to provide allocation context on the Schedule Board.

A resource allocation records requested time for project work, and a customer relationship management (CRM) task records a service visit and its assignees. A work calendar describes working days, hours, and exceptions. Displaying an allocation doesn't establish that a service visit has been scheduled or completed.

Record Information

The following table identifies the resource allocation record and its supported identifiers.

Property	Value
Record type	Standard NetSuite
Record name	Resource Allocation
SuiteScript record and FSM search type	`resourceallocation`
REST record ID	`resourceAllocation`
Record identity	NetSuite Internal ID (`internalid` in searches)
FSM use	Allocation context on the Schedule Board

Property

Value

Record type

Standard NetSuite

Record name

Resource Allocation

SuiteScript record and FSM search type

resourceallocation

REST record ID

resourceAllocation

Record identity

NetSuite Internal ID (internalid in searches)

FSM use

Allocation context on the Schedule Board

The Board's mapped event ID, resourceallocations-<internal ID>, identifies the displayed event. It is not another NetSuite record type. For native record access, see Resource Allocation - SuiteScript and Resource Allocation - REST.

Forms

NetSuite provides a resource allocation form. You can use custom forms to change how the resource allocation form appears. The Custom Form field ID is customform. Form labels don't change the underlying field IDs. For information about the Custom Form field and other native identifiers, refer to the Resource Allocation Records Browser.

The Schedule Board reads allocation data through searches and mappings. Its allocation block doesn't use the allocation's NetSuite form to generate fields.

Record Relationships

The following table lists the native record references and search joins used for resource allocations.

Related Record	Relationship and Field ID	Purpose
Resource	Resource field: `allocationresource` (SuiteScript), `allocationResource` (REST). Schedule Board search: `employee.internalid`.	Identifies the allocated resource. The standard FSM Board uses the Employee relationship.
Project	Customer:Project field: `project`. Schedule Board search join: `job`.	Identifies the project receiving the time. Several allocations can refer to one project.
Project Task	Optional Project Task field: `projectTask` (REST). Schedule Board search: `projecttask.internalid`.	Identifies the task within the project when allocating directly to a project task.
Requested By	Requested By field: `requestor` (SuiteScript), `requestedBy` (REST), `requestedby` (search).	Identifies the requester separately from the allocated resource.
Customer	The Board reads `customer.internalid` and customer name fields through the native search join.	Provides the allocation's customer context and displayed label. This search join is not an FSM custom customer field on the allocation.

Related Record

Relationship and Field ID

Purpose

Resource

Resource field: allocationresource (SuiteScript), allocationResource (REST). Schedule Board search: employee.internalid.

Identifies the allocated resource. The standard FSM Board uses the Employee relationship.

Project

Customer:Project field: project. Schedule Board search join: job.

Identifies the project receiving the time. Several allocations can refer to one project.

Project Task

Optional Project Task field: projectTask (REST). Schedule Board search: projecttask.internalid.

Identifies the task within the project when allocating directly to a project task.

Requested By

Requested By field: requestor (SuiteScript), requestedBy (REST), requestedby (search).

Identifies the requester separately from the allocated resource.

Customer

The Board reads customer.internalid and customer name fields through the native search join.

Provides the allocation's customer context and displayed label. This search join is not an FSM custom customer field on the allocation.

Native NetSuite supports resource choices beyond employees. The standard FSM allocation search uses the Employee join; native eligibility alone doesn't establish that a vendor or generic-resource allocation appears on the Board. See Resource Allocations for native project and task allocation behavior.

A project-level allocation is distinct from assignment to a particular task. Allocating a resource directly to a project task also assigns the resource to that project task. This allocation doesn't populate Assigned To (assigned) or Field Service Team (custevent_nx_task_team) on a CRM task. See FSM CRM Task Record.

FSM Fields

The following table lists native allocation fields used by FSM. IDs are SuiteScript field IDs unless identified as search IDs. Field labels can vary by account.

Field	Field ID	Meaning and Values
Start Date	`startdate`	First date of the allocation.
End Date	`enddate`	Last date of the allocation. The Board represents these dates from 00:00:00 on the first date through 23:59:59 on the last date. These displayed times are generated by the mapping.
Allocate	`allocationamount`	Requested quantity, interpreted using Allocation Unit.
Allocate By (search label)	`allocationunit`	Hours (`H`) or Percent of Time (`P`). Defines the units of the requested quantity. REST documentation calls this field Allocation Unit.
Number of Hours	`numberhours`	Hours represented by the allocation, displayed in Board details.
Percentage of Time	`percentoftime`	Percentage represented by the allocation, displayed in Board details.
Allocation Type	`allocationtype`	Hard (`1`) or Soft (`2`). The Board uses the type for allocation presentation.
Requested By	`requestedby` (search)	Requester displayed in Board details. For the stored relationship, use `requestor` in SuiteScript or `requestedBy` in REST.
Notes	`notes`	Allocation notes. The standard Schedule Board details show up to the first 1,000 characters. This preview doesn't replace the stored text.

Field

Field ID

Meaning and Values

Start Date

startdate

First date of the allocation.

End Date

enddate

Last date of the allocation. The Board represents these dates from 00:00:00 on the first date through 23:59:59 on the last date. These displayed times are generated by the mapping.

Allocate

allocationamount

Requested quantity, interpreted using Allocation Unit.

Allocate By (search label)

allocationunit

Hours (H) or Percent of Time (P). Defines the units of the requested quantity. REST documentation calls this field Allocation Unit.

Number of Hours

numberhours

Hours represented by the allocation, displayed in Board details.

Percentage of Time

percentoftime

Percentage represented by the allocation, displayed in Board details.

Allocation Type

allocationtype

Hard (1) or Soft (2). The Board uses the type for allocation presentation.

Requested By

requestedby (search)

Requester displayed in Board details. For the stored relationship, use requestor in SuiteScript or requestedBy in REST.

Notes

notes

Allocation notes. The standard Schedule Board details show up to the first 1,000 characters. This preview doesn't replace the stored text.

When you create an allocation with SuiteScript, set the quantity through allocationamount and the unit through allocationunit. SuiteScript returns Number of Hours and Percentage of Time as read-only values. For UI editing and recalculation rules, see Resource Allocations. See Resource Allocation - SuiteScript.

Hard indicates a commitment to the requested dates and hours. Soft indicates flexibility to adjust those dates and hours for other priorities. Selecting Hard doesn't prevent record edits. Percentage-based allocation uses the resource's work calendar to calculate hours. See Resource Allocations.

Creation and Update Sources

The following table describes how each source creates, updates, or displays allocation data.

Source	Record Effect
Native NetSuite entry	Creates or edits an allocation, including entry from a project or project task. Native entry can also define a recurring allocation schedule.
Supported native integration	Can create or update allocation data through the applicable NetSuite API and record requirements.
FSM Schedule Board	Retrieves and displays allocation data as read-only context. It doesn't save allocation date, amount, or resource changes through task dragging.

Source

Record Effect

Native NetSuite entry

Creates or edits an allocation, including entry from a project or project task. Native entry can also define a recurring allocation schedule.

Supported native integration

Can create or update allocation data through the applicable NetSuite API and record requirements.

FSM Schedule Board

Retrieves and displays allocation data as read-only context. It doesn't save allocation date, amount, or resource changes through task dragging.

Native allocation recurrence is separate from FSM case and task recurrence. Use Creating a Resource Allocation Record for native entry and recurrence.

Used by FSM Features

The following table describes how FSM Service Scheduling and Assignment uses resource allocations.

Feature	Record Use
FSM Service Scheduling and Assignment	Displays allocation context when Project Management and Resource Allocations are enabled. The standard search returns allocations for requested employees when the allocation dates overlap the Schedule Board date range.

Feature

Record Use

FSM Service Scheduling and Assignment

Displays allocation context when Project Management and Resource Allocations are enabled. The standard search returns allocations for requested employees when the allocation dates overlap the Schedule Board date range.

The allocation block spans full dates even when fewer hours are allocated. Check Allocate By, Number of Hours, and Percentage of Time for the allocation quantity. Allocation display doesn't prevent overlapping service-task assignments. For information about search selection, filters, and presentation, see FSM Schedule Board Configuration.

Record Constraints and Data Requirements

Native creation requires an eligible resource, project, allocation quantity, allocation type, and start and end dates. Select the quantity's allocation unit. A project task is optional for a project-level allocation. Creation requirements depend on the form or integration used. The Schedule Board applies separate employee and date search conditions to determine visibility.

Work-calendar data supports native conversion and distribution of allocated time. It is not stored as an FSM Work Calendar relationship on the allocation. Native allocation dates don't limit the time frame or duration of project tasks assigned to the resource.

The standard FSM allocation mapping supplies no allocation-processing request or completion indicator. A displayed block is allocation data, not evidence of a running script or completed service work.