Overview
DemandFlow provides several read-only field types for displaying information derived from the record's relationships and position in the data hierarchy:
- Parent Link (
parentLink) — displays the parent record's name as a clickable link - Related Property (
relatedProperty) — displays a property value from a related record - Combo Key Lookup (
comboKeyLookup) — resolves and displays a value from the record's hierarchical key - Combo Lookup (
comboLookup) — an alternative format for displaying key-based references - Combo Key Entity (
comboKeyEntity) — extracts and displays the entity type from a hierarchical key
All of these field types are read-only — they display derived information and cannot be directly edited.
Parent Link
The Parent Link field displays the name of the parent record in the hierarchy. When clicked, it navigates to the parent record, allowing easy upward navigation through the data structure.
Properties
| Property | Required | Description |
|---|---|---|
| ID | Yes | The field identifier. |
| Type | Yes | Must be set to parentLink |
| Name | Yes | The display label (e.g. "Parent Project", "Belongs To"). |
| Width | No | The percentage width. |
Related Property
The Related Property field displays a value from a related record, such as a field from the parent or a linked entity. This is useful for showing inherited or contextual information without requiring users to navigate to the related record.
Key-Based Fields
The Combo Key Lookup, Combo Lookup, and Combo Key Entity fields extract information from the record's hierarchical key. These are specialised fields used primarily for navigation and context display in records that exist within a multi-level hierarchy.
Use Cases
- Parent navigation — showing which project a task belongs to, with one-click navigation
- Inherited context — displaying the parent's status or owner on child records
- Hierarchy display — showing where a record sits within the organisational structure
Best Practices
- Place Parent Link fields near the top of the form for immediate context
- Use Related Property fields sparingly — only for values that are genuinely useful to see without navigating to the related record
- Remember these fields are always read-only; the underlying value is managed by the relationship itself