PORT: Portfolio
The PORT entity represents a strategic collection of projects and programmes managed together to achieve organisational objectives.
PORT 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 PORT.Entity properties
| Property | Value |
|---|---|
| Entity code | PORT |
| Display name | Portfolio |
| Plural | Portfolios |
| Level | 100000 |
Use cases
PORT is the top-level container in the project management hierarchy (PORT > PROG > PJ). It groups related projects and programmes so they can be governed as a single investment. The comboFilterAdd SUB|ENT|BU|DIV|DEPT ties portfolios to the organisational hierarchy, enabling budget roll-up by entity/BU/division. Projects are linked via comboKey SUB|PORT|PJ. The definition includes CAPEX budget fields by year to support annual investment planning, a finance tracker (ft) for monthly spend tracking, costs rows for budget management, and a drawdown panel (DRAWDOWN entity) for roadmap drawdown tracking. Roles (portroles) capture portfolio-level governance assignments. The viewOptions support both a projectcontainers card view and a standard grid, reflecting that portfolios are primarily navigated as visual containers of their child projects.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
description | text (multi-line) | Description. | |
status | enum | Status. Valid ids: new (New), delivery (Delivery), closed (Closed). | |
f6132205-9122-409f-93ff-42d6e7d64814 | text | Project prefix. | |
53890bcc-5945-4291-8117-d7145ea1f2b1 | text | Active Infra code. | |
7d9db797-4663-4aeb-9535-8f3c220a569a | text | Infra codes. | |
7d9db797-4663-4aeb-9535-8f3c220a569a | simpleObjectLookup | Infra codes. | |
b7826c56-7059-43ff-ba89-0518e18d18b1 | text | TORO id. | |
u1759488177378 | text | Budget owner. | |
43b785fa-e71e-4531-83ed-2c2dfee195d2 | text | Business sponsor. | |
4a104a06-1352-4bc5-80bb-7c4e793f2379 | text | Executive sponsor. | |
ee10077a-b942-4c57-9b95-07c03d8fcaa2 | text | Clarity code. | |
b303275b-7b59-4f13-b9e0-6ca3ac6c9c6f | text | Workstream name. | |
40123ebb-82fa-4000-9bea-b3ae36ef99c9 | number | Approved CAPEX 2024. | |
c134c382-4ad7-4d08-bf76-e2c37256aa3c | number | Approved CAPEX 2025. | |
8d87174e-2a22-46e5-858e-68b8f2edbefd | number | Approved CAPEX 2026. | |
57a53688-1317-40e4-90a8-02253cbadc17 | number | Approved CAPEX 2027. | |
c0792629-3b01-4ccd-bdbd-96f12d09ae9b | number | Approved CAPEX 2028. | |
carbonReductionTarget | number | Target percentage reduction vs baseline. | |
targetBaselineYear | text | Baseline year. | |
totalKgCO2e | number | Aggregated from project carbon totals. Read-only. |
Additional panels
- Dashboard panel.
- progdepmap panel.
- portroles panel.
- costs panel.
- ft panel.
Relationships
- Related lists:
PJvia formatSUB|PORT|PJ;SCENARIOvia formatSUB|PORT;DRAWDOWNvia formatSUB|PORT.
Creating a Portfolio via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PORT",
"level": 100000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"description": "Long description text.",
"status": "new",
"f6132205-9122-409f-93ff-42d6e7d64814": "Example text"
}Listing PORT records
# All portfolios in your tenant
GET /v1/entities/PORT/SUB