SUBCOMPINV: Subcomponent
Installed subcomponent instance within a deployed asset, with its own serial number and port inventory.
SUBCOMPINV 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 SUBCOMPINV.Entity properties
| Property | Value |
|---|---|
| Entity code | SUBCOMPINV |
| Display name | Subcomponent |
| Plural | Subcomponents |
| Level | 100000 |
Use cases
Installed subcomponent instance within a deployed asset, with its own serial number and port inventory.
SUBCOMPINV is the inventory side of the subcomponent dual model (catalogue: SUBCOMP, inventory: SUBCOMPINV). While SUBCOMP defines what a subcomponent IS at catalogue level, SUBCOMPINV tracks a specific installed instance inside a deployed COMPINV asset. It inherits the catalogue structure (partNo, sku, price, vendor, classification via SUBCOMPTYPE) but adds instance-specific operational data. The isAsset and indAsset flags control whether this specific installed subcomponent is tracked as a separate financial asset or counted as bulk stock. The Ports panel links to COMPPORT via multigroup, carrying forward the port definitions for this subcomponent instance. SUBCOMPINV records are children of their parent COMPINV via the comboKey relationship format SUB|COMPINV, enabling the asset editor to show all installed subcomponents inline. This dual-model approach means you can have a catalogue SUBCOMP for '16GB DDR4 DIMM' and many SUBCOMPINV instances representing each physical stick installed across your estate.
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. |
Instance Details
| Field | Type | Required | Notes |
|---|---|---|---|
serial | text | Serial Number. | |
slotPosition | text | Which slot, bay, or DIMM socket this is installed in | |
operationalStatus | enum | Valid ids: working (Working), degraded (Degraded), failed (Failed), empty (Empty Slot), unknown (Unknown). | |
firmwareVersion | text | For smart optics, NICs, RAID controllers, etc. | |
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 | Weight (kg). 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": "SUBCOMPINV",
"level": 100000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"description": "Example text"
}Listing Subcomponents
GET /v1/entities/SUBCOMPINV/SUB