CABLEPATHWAYTYPE: Cable Pathway Type
Product catalog of cable pathway types including trays, conduits, ducts, and fittings with manufacturer specifications and dimensions.
Default definition. This article describes the default
CABLEPATHWAYTYPE 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 CABLEPATHWAYTYPE.Entity properties
| Property | Value |
|---|---|
| Entity code | CABLEPATHWAYTYPE |
| Display name | Cable Pathway Type |
| Plural | Cable Pathway Types |
| Level | 1000 |
Use cases
Product catalog of cable pathway types including trays, conduits, ducts, and fittings with manufacturer specifications and dimensions.
Fields
General: Identification
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | e.g. Legrand Cablofil CM50 Wire Mesh Tray |
category | enum | Yes | Category. Valid ids: 1 (Cable Tray), 2 (Conduit), 3 (Cable Duct / Raceway), 4 (Basket Tray), 5 (Fitting - Elbow), 6 (Fitting - Tee), 7 (Fitting - Cross), 8 (Fitting - Reducer), 9 (Fitting - Coupler), 10 (J-Hook), 11 (Rack Drop), 12 (Riser). |
manufacturer | reference → VEN | Manufacturer. | |
partNumber | text | Part Number. | |
modelName | text | Model / Series. | |
description | text (multi-line) | Description. | |
status | enum | Yes | Status. Valid ids: 1 (Active), 2 (Discontinued). |
General: Dimensions
| Field | Type | Required | Notes |
|---|---|---|---|
crossSection | enum | Cross Section. Valid ids: 1 (Rectangular), 2 (Circular). | |
widthMm | number | Internal usable width | |
heightMm | number | Internal usable height/depth | |
diameterMm | number | Internal diameter for circular conduits Visible when crossSection = 2. | |
wallThicknessMm | number | Wall Thickness (mm). | |
lengthMm | number | Standard section length (e.g. 3000mm for a 3m tray) | |
bendAngle | enum | For fitting types (elbows, tees) Valid ids: 1 (45°), 2 (90°). | |
bendRadiusMm | number | Minimum bend radius for fittings and fibre compliance |
Specifications: Physical
| Field | Type | Required | Notes |
|---|---|---|---|
material | enum | Material. Valid ids: 1 (Galvanized Steel), 2 (Stainless Steel), 3 (Aluminium), 4 (Wire Mesh / Basket), 5 (PVC), 6 (Fiberglass (FRP)), 7 (Concrete). | |
finish | enum | Finish. Valid ids: 1 (Hot-Dip Galvanized), 2 (Electro-Galvanized), 3 (Powder Coated), 4 (Stainless), 5 (Pre-Galvanized), 6 (None). | |
fireRating | enum | Fire Rating. Valid ids: 1 (None), 2 (1 Hour), 3 (2 Hour), 4 (3 Hour), 5 (Plenum Rated). | |
maxLoadKgM | number | Maximum supported load per metre | |
weightKgM | number | Self-weight per metre |
Specifications: Cable Capacity
| Field | Type | Required | Notes |
|---|---|---|---|
maxCableCount | number | Typical max cables at rated fill | |
crossSectionAreaMm2 | number | Internal usable cross-section area | |
maxFillPercent | number | Code-mandated maximum fill percentage (e.g. 40-50%) | |
ipRating | text | e.g. IP40, IP66 | |
notes | text (multi-line) | Notes. |
Relationships
- Lookups:
manufacturerpoints at aVENrecord. - Related lists:
CABLEPATHWAY(viapathwayTypeRef).
Creating a Cable Pathway Type via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "CABLEPATHWAYTYPE",
"level": 1000,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Name",
"category": "1",
"status": "1",
"description": "Description"
}Listing Cable Pathway Types records
GET /v1/entities/CABLEPATHWAYTYPE/SUB