Service order line items
A planned service on a service order, linked to the sold service item and optionally to the sales order line.
Fields
The API name is what the API, MCP and the CLI use.
| Name | API name | Type | Required | Description |
|---|---|---|---|---|
| ID | id | Record ID | Yes | |
| Order | serviceorderId | Reference | Yes | |
| Item | serviceitemId | Reference | Yes | |
| Quantity | quantity | Quantity | Quantity in the catalog unit after any unit conversion on the line. | |
| Unit | catalogunit | Unit | ||
| Line item | salesorderitemId | Reference | ||
| Created by | createdBy | User | ||
| Created at | createdAt | Date and Time | Yes | |
| Updated by | updatedBy | User | ||
| Updated at | updatedAt | Date and Time | Yes | |
| Confirmed by | confirmedBy | User | ||
| Confirmed at | confirmedAt | Date and Time | ||
| Blocked by | blockedBy | User | ||
| Blocked at | blockedAt | Date and Time | ||
| Archived by | archivedBy | User | ||
| Archived at | archivedAt | Date and Time |
Relations
Owned records (solid line) are deleted with their owner. Grouped records (dashed line) can exist alone.
| Field | Points to | Kind |
|---|---|---|
Order serviceorderId | Service orders | owned by |
Item serviceitemId | Service items | reference |
Line item salesorderitemId | Sales order line items | reference |
Actions
What you can do with a record. Every action also sends the webhook event serviceorderitems.<action>. Reads (find, get, count) work on every table.
| Name | API name | Description | Where |
|---|---|---|---|
| Create | create | Add a new line item. | App · WebMCP · API · MCP · CLI |
| Edit | update | Save changes to this line item. | App · API · MCP · CLI |
| Delete | delete | Delete this line item and the data that belongs with it. This cannot be undone. | App · WebMCP · API · MCP · CLI |