RES: Resource
The RES entity: A billable resource definition with day rate, spend type classification, and area assignment for finance tracking.
RES 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 RES.Entity properties
| Property | Value |
|---|---|
| Entity code | RES |
| Display name | Resource |
| Plural | Resources |
| Level | 250 |
Use cases
RES represents a resource that can be allocated to projects for financial planning and tracking. Unlike STF (which represents a specific person), RES is more abstract - it defines a resource role or position with a day rate for cost modelling. The spend type (SPEND entity lookup, required) classifies the cost category for financial reporting (e.g., CAPEX vs OPEX).
The legacy type field (Contingent, Internal, 3rd Party, External) is being replaced by the spend type lookup for more flexible classification. The area field uses simpleObjectLookups (a dynamic lookup to a configurable list entity) for custom area/location classification. Status (Active/Archived) controls visibility in resource selection.
Fields
Brief
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name |
description | text (multi-line) | Description | |
type | enum | Resource type (Legacy) Valid ids: Contingent (Contingent), Internal (Internal), 3rd Party (3rd Party), External (External). | |
spendtype | reference → SPEND | Yes | Spend type |
status | enum | Yes | Status Valid ids: Active (Active), Archived (Inactive). |
price | number | Yes | Day rate |
area | reference → custom list | Area | |
carbonProfile | reference → CARBONPROFILE | Equipment usage template for carbon calculation |
Relationships
- Lookups:
spendtypepoints at aSPENDrecord;areapoints at a configurable list;carbonProfilepoints at aCARBONPROFILErecord.
Creating a Resource via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "RES",
"level": 250,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"spendtype": "",
"status": "Active",
"price": 1
} Listing Resources records
GET /v1/entities/RES/SUB