SUBCOMP: Subcomponent
Catalogue entry for a subcomponent that sits inside a parent component, with its own specs and port definitions.
SUBCOMP 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 SUBCOMP.Entity properties
| Property | Value |
|---|---|
| Entity code | SUBCOMP |
| Display name | Subcomponent |
| Plural | Subcomponents |
| Level | 100000 |
Use cases
Catalogue entry for a subcomponent that sits inside a parent component, with its own specs and port definitions.
SUBCOMP is the catalogue side of the subcomponent dual model (catalogue: SUBCOMP, inventory: SUBCOMPINV). It defines internal parts that sit inside a parent COMP, such as line cards, power supplies, fans, or storage modules. Like COMP, it carries catalogue-level attributes: partNo, sku, price, vendor (OEM), and classification (via SUBCOMPTYPE). The isAsset and indAsset flags control whether deployed instances are tracked as individual financial assets or bulk stock. EOSL tracks end-of-service-life dates from the manufacturer. Physical dimensions mirror the parent COMP structure for space planning. The Ports panel uses a multigroup relationship to COMPPORT, allowing subcomponents to define their own port layouts at the catalogue level. When a COMP is deployed, its SUBCOMP children spawn SUBCOMPINV records that inherit catalogue properties but add instance-specific data like serial numbers. The parent-child relationship between COMP and SUBCOMP is managed via multigroup, meaning subcomponents are created and managed inline within the parent component editor.
Fields
Basic Information
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Component Name. |
description | text (multi-line) | Description. | |
partNo | text | Part number. | |
sku | text | SKU. | |
price | number | Cost. | |
vendor | reference → VEN | OEM. | |
class | reference → SUBCOMPTYPE | Classification. |
Details
| Field | Type | Required | Notes |
|---|---|---|---|
isAsset | boolean | Finance asset. | |
indAsset | boolean | Individual stock. | |
eosl | date | EOSL. | |
breakpoints | text (multi-line) | Breakpoints. |
Dimensions
| Field | Type | Required | Notes |
|---|---|---|---|
dimHeight | number | Height (mm). Read only. | |
dimWidth | number | Width (mm). Read only. | |
dimDepth | number | Depth (mm). Read only. | |
weight | number | Depth (mm). Read only. |
Relationships
- Lookups:
vendorpoints at aVENrecord;classpoints at aSUBCOMPTYPErecord.
Creating a Subcomponent via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SUBCOMP",
"level": 100000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"description": "Example text"
}Listing Subcomponents
GET /v1/entities/SUBCOMP/SUB