FSM Project Task Record

A project task represents work within a NetSuite project. It supports project planning, resource assignments, and dependencies, including work that spans several days. In Field Service Management (FSM), the Schedule Board and FSM Mobile use the project task's service information. This includes its service classification, related customer and asset, location, and recorded service timestamps.

A project task is separate from a customer relationship management (CRM) task. Linking a CRM task to a project doesn't change its record type or give it project task resource assignments. For information about the native planning model, see Project Tasks.

Record Information

The following table lists the record identifiers and FSM mappings.

Property	Value
Record type	Standard NetSuite
Record name	Project Task
Record ID	projecttask
Record identity	NetSuite Internal ID (internalid)
FSM model	models/projecttask
FSM classification	Field Service Task Type (custevent_nx_task_type)
Project relationship	Native Project Name (company). job is the project search join
Resource assignments	Native assignee sublist. projecttaskassignment is the assignment search join

These identifiers distinguish stored record data from FSM model attributes, search joins, and labels on customized forms. For information about native field and sublist IDs, refer to the Project Task Records Browser.

Forms

Use the standard NetSuite project task form or an account-created custom project task form. Custom Form (customform) selects the entry form. The supplied FSM forms don't include a separate FSM Project Task form. For native entry and customization, see Creating a Project Task Record.

Form choice affects the visible fields and entry requirements. Preferred-form and saved-form behavior depends on the applicable NetSuite form settings. If Store Form with Record is available and checked, NetSuite retains that form for records created with it. For information about settings that vary by form type, see Custom Entry Form Properties.

FSM Mobile loads a project task as an event and presents its configured resources. A resource can use explicit elements or generate elements from a configured NetSuite form. Generating those elements is separate from selecting or retaining the project task's NetSuite UI form. The standard Details resource uses explicit elements for Actions Taken. It doesn't load the entire project task form. For information about form loading and overrides, see Form Properties.

Record Relationships

The table identifies the record holding each relationship. Native project relationships and supplied FSM links have different purposes.

Related Record	Relationship and Field ID	Purpose
Project	Project task Project Name (company) references one project (job). A project can contain several project tasks.	Supplies the required project context. FSM reads the project's customer, asset, and, in OneWorld, subsidiary.
Parent project task	Project task Parent Task (parent) references another project task.	Organizes native task hierarchies. A parent task summarizes its children and has no resource assignments.
Predecessor project task	Project task predecessor sublist holds Task (task) and dependency Type (type).	Defines native planning dependencies. This relationship is separate from the Parent Task hierarchy.
Employee resource	Project task assignee sublist holds Resource (resource). Searches use projecttaskassignment.resource.	Stores multiple resource assignments. There is no designated lead or separate FSM team-member role.
Customer	Project task Field Service Customer (custevent_nx_customer) references the customer. Project Field Service Customer (custentity_nx_customer) supplies the project's service customer.	Keeps customer available separately from Project Name.
Asset	Project task Field Service Task Asset (custevent_nx_task_asset) references customrecord_nx_asset. Project Field Service Asset (custentity_nx_asset) supplies the project's asset.	Identifies the equipment or site and supplies service-location context.
Task Type	Project task Field Service Task Type (custevent_nx_task_type) references customrecord_nx_task_type.	Supplies the FSM classification used by applicable rules and capabilities.
Contact	Project task Contact (contact) references a contact.	Provides contact context separately from the customer signatory text.
Time Bill	Time Bill native event field (casetaskevent) and Field Service Project Task (custcol_nx_projecttask) hold links to the project task in the standard Time workflow in FSM Mobile.	Associates separately saved employee time with the work.
Transaction	Transaction body Field Service Project Task (custbody_nx_projecttask) and applicable line Field Service Project Task (custcol_nx_projecttask) reference the project task.	Associates orders, fulfillments, and expenses with the work. Body and line links are separate.
Installation, Maintenance, Repair, or Uninstallation	The related record holds custrecord_nx_install_project_task, custrecord_nx_maintenance_project_task, custrecord_nx_repair_project_task, or custrecord_nx_uninstall_project_task.	Supplies a project task reference for separately recorded service work. FSM Mobile inclusion and requirements depend on its configured resource.

FSM sources customer and asset from the selected project. If a customer or asset value conflicts with the selected project's value, FSM can restore the project's value on the project task. FSM doesn't replace the project task's project relationship with a customer. See FSM Customer and Asset Selection.

The standard project task event in FSM Mobile has no case context. Sharing a project with a case doesn't establish a direct project task-case relationship. An account custom link doesn't automatically add case inheritance, FSM Mobile resources, history, reports, or synchronization behavior.

FSM Fields

The tables include significant native fields and the supplied FSM fields relevant to project tasks. Labels shown are the supplied English labels. Account labels and presentation can differ.

Identity and Classification with Work Details

The following table lists project task identification, classification, and work-detail fields.

Field	Field ID	Meaning and Important Values
Project Task Name (native)	title	Names the work. The standard project task model doesn't supply the CRM task automatic-name formula.
Field Service Task Number	custevent_nx_task_number	FSM supplies the internal ID when this field is empty and clears the field when copying a record through the project task model. This field is separate from Project Task Name.
Field Service Task Type	custevent_nx_task_type	Classifies the service work. A populated value participates in FSM Mobile selection and report-button eligibility, with additional conditions for each capability.
Priority (native)	priority	Priority used in FSM displays. It is separate from Status and resource assignment.
Notes (native)	message	Description or instructions for the work.
Field Service Actions Taken	custevent_nx_actions_taken	Records work performed. Details, service history, and service reports use this field.
Field Service Customer Name	custevent_nx_customer_name	Names the customer signatory. It is not the customer record link.
Field Service Customer Signature	custevent_nx_customer_signature	Stores customer signature content.
Field Service Sign Off Technician	custevent_nx_signoff_technician	Employee reference for technician sign-off. It doesn't designate a lead resource.
Field Service Technician Signature	custevent_nx_technician_signature	Stores technician signature content.

Signature content and sign-off references don't establish Completed status. For NetSuite signature controls, see Signature Pads.

Schedule and Work with Actual Timestamps

The following table describes fields for the project task's schedule, work, and actual timestamps.

Field	Field ID	Meaning and Important Values
Start Date / Start Time (native)	startdate, starttime	Native planned start. Fixed Start permits a specified start. Other constraints use project scheduling.
End Date (native)	enddate	Native task end, affected by project scheduling and recorded work. It is separate from Field Service End.
Constraint Type (native)	constrainttype	Native scheduling constraint. Fixed Start is FIXEDSTART in the FSM Board eligibility mapping.
Planned Work / Estimated Work (native)	plannedwork, estimatedwork	Native planning measures. Board saves write resource Planned Work when that feature is enabled, otherwise resource Estimated Work.
Actual Work (native)	actualwork	Time entered against the task, in hours, separate from the elapsed interval between Field Service Start and End.
Field Service Time Zone	custevent_nx_time_zone	References customrecord_nx_time_zone and holds service-time context. It doesn't add CRM task date and time conversion.
Field Service Start	custevent_nx_task_start	Actual service Start action timestamp, stored with date and time zone.
Field Service End	custevent_nx_task_end	Actual service Complete action timestamp, stored with date and time zone.
Field Service On Site / Off Site	custevent_nx_task_onsite, custevent_nx_task_offsite	Recorded arrival and departure timestamps. These differ from Start and Complete.

Resource assignments also hold Units (assignee.units), expressed as a percentage, work (assignee.plannedwork or assignee.estimatedwork), Service Item (assignee.serviceitem), Unit Cost (assignee.unitcost), Unit Price (assignee.unitprice), and applicable Billing Class (assignee.billingclass). These describe resource planning and costing, rather than an FSM primary assignee and Task Team.

Board saves can recalculate work using resource calendars and Units, so the saved dates can differ from the proposed interval. See FSM Service Scheduling and Assignment.

Project tasks don't use custevent_nx_start_date, custevent_nx_start_time, custevent_nx_end_date, and custevent_nx_end_time. Those separate schedule fields belong to cases and CRM tasks. See FSM Service Time Zone Sourcing and Synchronization.

Service Location

The following table lists project task service-location fields.

Field	Field ID	Meaning and Important Values
Field Service Address	custevent_nx_address	Saved service-address text. A linked asset can supply it.
Field Service Latitude / Longitude	custevent_nx_latitude, custevent_nx_longitude	Saved coordinates used for maps, navigation, and proximity checks.
Field Service Geolocation	custevent_nx_geo_location	Combined coordinate text maintained by geocoding or migration. Maps use the separate coordinate fields.
Field Service Geolocation Compliant	custevent_nx_geo_location_comp	Compatibility indicator for earlier coordinate-compliance processing. Its supplied checkbox default is checked. It doesn't establish location accuracy or a running execution.

Asset sourcing can replace a project task's address and coordinates when saved. Background propagation of later asset location changes has its own selection rules. See FSM Service Locations and Geocoding. Arrival, departure, and navigation behavior belongs to FSM Maps and Location Tracking.

Status and Processing with Compatibility Data

The following table describes project task status, processing, and compatibility data.

Field or Indicator	Field ID	Meaning and Important Values
Status (native)	status	Not Started (NOTSTART), In Progress (PROGRESS), or Completed (COMPLETE). Describes business state, not script execution.
Field Service Pending Notifications	custevent_nx_notification_pending	Stores queued notification requests. Manual report requests and qualifying configured Task Type/status changes can add requests. Notification processing clears requests after the corresponding notification records exist. An empty field doesn't confirm that notifications were sent or delivered.
Sending Notification banner	No stored project task field	Reports assessed outstanding notification work. It doesn't establish that an email is currently being sent.
Field Service Idempotency Key	custevent_nx_idempotency_key	Older custom identity field retained for compatibility. It is not a project task work-completion indicator.
External ID (native)	externalid	Native integration identity. Standard FSM Mobile record creation uses this field for request identity rather than the older custom key. That mechanism doesn't itself provide a project task creation action.
Field Service Close Case	custevent_nx_case_closed	Shared field also present on project tasks. The standard Project Task Details resource hides its control. A checked value is not evidence that a project task closed a case.

Synchronization of project tasks in FSM Mobile can change native Status when Start or Complete is submitted. Capturing an action locally in FSM Mobile doesn't confirm that NetSuite has accepted the update. CRM task background status and automatic activity-time processing must not be inferred from shared timestamp fields.

Notification requests use Field Service Scheduled : Notification (customdeploy_nx_notification). A cleared request or completed execution doesn't prove every intended action succeeded. Field Service Error records can hold affected-record references. The project task has no dedicated FSM Error link field. See FSM Script Reference and Field Service Error Record for execution and error data, and FSM Service Reports and Notifications for notification outcomes.

Creation and Update Sources

The following table lists how project tasks are created and updated.

Source	Effect on the Record
Native project entry and planning	Creates project tasks in project context and maintains native planning relationships. See Creating a Project Task Record.
FSM record handling	Maintains Task Number, sources customer, asset, and service time zone, and applies relevant location, signature, and notification handling.
Schedule Board	Saves supported changes to native planned start and resource assignments, including resource-work calculations.
FSM Mobile	Synchronizes mapped service details, timestamps for Start, Complete, arrival, and departure, and corresponding status changes. Related time entries and transactions are saved separately.
Asset location processing	Can update differing locations on linked Not Started project tasks.
Geolocation and notification processing	Maintains coordinate data or notification requests through their separate processing paths.

The supplied record deployments are Field Service User Event (customdeploy_nx_projecttask_userevent) and Field Service Client (customdeploy_nx_projecttask_client). For script identifiers and operational controls, see FSM Script Reference.

Case Add Tasks and the standard actions for creating work in FSM Mobile create CRM tasks. These actions don't create project tasks.

Used by FSM Features

The following table describes how FSM features use project tasks.

Feature	How the Project Task Is Used
FSM Service Scheduling and Assignment	Supplies project work, native dates, and resource assignments.
FSM Customer and Asset Selection	Keeps service relationships consistent with the project.
FSM Service Locations and Geocoding	Maintains the saved destination location.
FSM Maps and Location Tracking	Uses coordinates and records arrival/departure timestamps.
FSM Service Reports and Notifications	Uses saved work details and separately linked time, transaction, and file data.
FSM Mobile Sales Order Management	Supplies project task relationships on orders and lines.
FSM Mobile Quote Management	Supplies project task relationships on estimates and their lines. Sharing a project alone doesn't select another quote.
FSM Service Time Tracking	Provides separate manual Time tab entry. Automatic Track Service Time excludes project tasks.

Record Constraints and Data Requirements

A project task requires project context. The 22 supplied FSM custom fields enabled for project tasks are not marked as required in the field definitions. Native record validation, the selected form, FSM Mobile elements, and individual capabilities can require additional data. The standard project task model has no explicit initial defaults. Native NetSuite defaults and the account's form requirements still apply.

FSM scheduling and FSM Mobile use project tasks when NetSuite Project Management is enabled. Technician assignment uses Project Resources. Assignment alone doesn't ensure that a project task appears in FSM Mobile or that you can edit it on the Schedule Board. FSM Mobile and the Schedule Board apply separate selection and access conditions.

Important: Automatic Track Service Time supports CRM tasks only. It is an account-wide control and must not be enabled when both CRM tasks and project tasks are displayed in FSM Mobile. The manual Time tab is configured separately. Start and End timestamps don't establish that time bills were created. See FSM Service Time Tracking.

Project tasks don't support the FSM Consumables model. Use the supported Sales Order workflow for parts, subject to its transaction and fulfillment limits. See FSM Project Tasks and FSM Mobile Sales Order Management.

Additional Information

• FSM Service Scheduling and Assignment
• Time Tab in FSM Mobile
• FSM Service Reports and Notifications

Related Topics

• FSM Records
• FSM Employee Record
• FSM Project Record
• FSM Task Type Record
• FSM Time Bill Record

General Notices