DEPT: Department
A department within a division with staff members, annual budgets, cost centre, and spending approval authority.
DEPT definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches DEPT.Entity properties
| Property | Value |
|---|---|
| Entity code | DEPT |
| Display name | Department |
| Plural | Departments |
| Level | 2000 |
Use cases
DEPT is the fourth level of the organisational hierarchy (ENT > BU > DIV > DEPT) and the primary operational unit. It links to its parent division via comboKeyLookup to DIV. Staff members (DEPTSTF) are children via comboKey SUB|DEPT. Departments have financial management capabilities: annual budget fields (budget24/25/26), cost centre code, and a manager with automatic approval limit (autoApprove) for spending authorisation. The domainstats custom row type provides department-level analytics. Domain objectives (DOBJ) reference departments as their 'domain', and initiatives (INI) link to departments for ownership. The panel2 property (KPIs) appears to be an unused/alternate panel definition. The comboKey chain SUB|ENT|BU|DIV|DEPT provides full ancestry for hierarchical reporting and budget roll-up. AI features support divisional analysis.
Fields
Information
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
shortName | text | Short Name. | |
code | text | Department Code. | |
entityCode | comboKeyLookup | Division. | |
costCentre | text | Cost centre. | |
description | text (multi-line) | Description. |
Budgets
| Field | Type | Required | Notes |
|---|---|---|---|
budget24 | number | 2024. | |
budget25 | number | 2025. | |
budget26 | number | 2026. |
Manager
| Field | Type | Required | Notes |
|---|---|---|---|
manager | reference → user | Select Manager. | |
autoApprove | number | Automatic approval limit. |
Relationships
- Related list:
STF, related list.
Creating a Department via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "DEPT",
"level": 2000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"shortName": "Example value",
"code": "Example value",
"costCentre": "Example value"
}Listing Departments records
GET /v1/entities/DEPT/SUB:<your-sub-id>