DemandFlow Support Centre

DIV: Division

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A division within a business unit, containing departments and tracking performance metrics.

DIV: Division

A division within a business unit, containing departments and tracking performance metrics.

Default definition. This article describes the default DIV 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 DIV.

Entity properties

PropertyValue
Entity codeDIV
Display nameDivision
PluralDivisions
Level2000

Use cases

DIV is the third level of the organisational hierarchy (ENT > BU > DIV > DEPT). It uses comboLookup to reference its parent BU, deriving the relationship from the comboKey chain. Departments (DEPT) are children via comboKey SUB|ENT|BU|DIV|DEPT. The structure mirrors BU closely with name/shortName/code, regional information, contact details, and KPI metrics (headcount, revenue, operating cost, EBITDA). AI features (ai:true, context.getDivisonUnitData) enable analysis at the division level. The progressive comboKey chain (SUB|ENT|BU|DIV) maintains the full ancestry path, enabling navigation up and down the hierarchy. This entity exists to model organisations where business units are further subdivided before reaching the department level.

Fields

Basic Info

FieldTypeRequiredNotes
nametextYesDivison Name.
shortNametextShort Name.
codetextDivision Code.
entityCodecomboLookupBusiness Unit.
managerreference → userDivision Manager.

Contact & Region

FieldTypeRequiredNotes
regiontextRegion.
countrytextCountry.
contactEmailtextContact Email.
websitetext (URL)Division Link.

Relationships

  • Related list: DEPT, comboKey format SUB|ENT|BU|DIV|DEPT.

Creating a Division via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "DIV",
  "level":    2000,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example name",
  "shortName": "Example value",
  "code": "Example value",
  "region": "Example value"
}

Listing Divisions records

GET /v1/entities/DIV/SUB:<your-sub-id>

See also

divdivisiondivisionsdivisonswithinbusinessunitcontainingdepartmentstrackingperformance

Was this article helpful?

← Back to Knowledge Base