Actions156
- Customer Actions
- Resource Actions
- Order Actions
- Item Actions
- Job Actions
- Item Prices Actions
- Job Prices Actions
- Files Actions
- Custom Fields Actions
- Admin Actions
- Customer Address Actions
- Customer Fields Actions
- Get Many by External ID
- Get Many Customer Objects (By Status)
- Get Many Customer Objects (By Status List)
- Get Available Account IDs
- Get Available Payment Methods
- Get Available Workflows
- Get Account
- Get Payment Information
- Get Payment Method Description
- Get Created By Resource ID
- Get Project Manager ID
- Get Source of Contact
- Get Date of Initial Contact
- Get Dossier
- Update Payment Information
- Update Project Manager ID
- Update Source of Contact
- Update Date of Initial Contact
- Update Dossier
- Resource Fields Actions
- Order Fields Actions
- Get Creation Date
- Get Delivery Comment
- Get External ID
- Get Language Combination
- Get Links
- Get Master Project ID
- Get Order Closing Date
- Get Order Confirmations
- Get Order Date
- Get Order Number for View
- Get Project Category
- Get Project Status
- Get Request ID
- Get Subject
- Create Project Linking
- Get List of Templates
- Set Request ID
- Set Creation Date
- Set EN15038 Requested
- Set External ID
- Set Master Project ID
- Set Project Category
- Item Fields Actions
- Job Fields Actions
- Update Job Status
- Run Automatic Job
- Get Comment
- Update Comment
- Get Description
- Update Description
- Get Due Date
- Update Due Date
- Get Delivery Date
- Get Creation Date
- Get Job Number
- Get Currency
- Get Resource ID
- Update Contact Person ID
- Get Contact Person ID
- Get Delivery Note
- Update Delivery Note
- Get Payable ID
- Update CAT Report
- Customer Contact Actions
Item → Update Item
AI-generatedSummary
Updates an existing Plunet item.
Inputs
- itemID (required) — The numeric ID of the item to update (must be >0).
- projectType — The project type of the item. Options: Quote (1) or Order (3). Defaults to Order (3).
- projectID — The numeric ID of the project the item belongs to. Defaults to 0 (no project).
- enableNullOrEmptyValues — When true, allows setting fields to null or empty values during the update. Defaults to false.
- additionalFields — Collection of optional fields to update on the item after the base update. Sub‑fields are described below.
Output shape
JSON object containing the updated item as returned by the Plunet API (exact structure depends on the API response).
The operation maps internally to the 'update' operation on the 'DataItem30Core' resource. Provide at least the itemID; other parameters are optional. If enableNullOrEmptyValues is true, you can clear a field by sending an empty string or null via the corresponding sub‑field in additionalFields.
Examples
Example 1: Update an item’s brief description and status.
Set itemID to 123, leave projectType and projectID at defaults, enableNullOrEmptyValues false, and in additionalFields set Brief Description = 'New description' and Status = 'Delivered (2)'.
