multiItem Property
| Name | Type | Default | Description |
|---|---|---|---|
multiItem | boolean | false | Indicates this column displays multiple related items (one-to-many or many-to-many relationship). Enables multi-value display and editing. |
multiItem is set to true, the column cell renders all linked entities for the current row, rather than a single value. Users can add, remove, and browse multiple related items through a dedicated picker interface.
When to Use Multi-Item Columns
Multi-item columns are required in these scenarios:| Scenario | Example Binding Path | Description |
|---|---|---|
| Second linked entity on same parent | systemRequirements.systemRequirement.designRequirements.designRequirement | When a parent entity links to two different entity types via separate relationships |
| Verification/validation test cases | systemRequirements.systemRequirement.verificationTestCases.verificationTestCase | Test case collections linked to requirements |
| External references | designRequirements.designRequirement.externalReferences.externalReference | External system links attached to design items |
Column Configuration Properties
The following properties apply when configuring a multi-item column:| Name | Type | Default | Description |
|---|---|---|---|
multiItem | boolean | false | Enables multi-item display and editing for the column |
title | string | None | Display label for the column header |
width | number | None | Column width in pixels |
header | string | None | YAML anchor reference to reusable header styling configuration |
display | string | id | Specifies which property of the referenced entity to display. Options: title, titleOrName, or a custom property path |
columnGroup | string | None | Assigns the column to a visual column group |
visible | boolean | true | Controls whether the column is shown by default |
formatter | string | None | References a formatter name from the formatters section |
isreadOnly | boolean | false | Prevents user editing of this column (deprecated in favor of formatter=readOnly) |
Binding Path Syntax
Multi-item columns use dot-separated binding paths that follow the relationship chain defined in the domain model. The path alternates between the collection navigation property and the entity type:Configuration Example
The following example adds an external references multi-item column to a design requirement:Sources Configuration
Multi-item columns require their expansion paths to be declared in thesources section. The expand array must include the full chain of relationships:
Match Sources to Columns
Match Sources to Columns
Every multi-item column binding path must have a corresponding expansion path in the
sources configuration. If the expansion is missing, the column will not load related entities.Domain Model Requirements
The entity types and relationships referenced by multi-item columns must exist in the domain model:Export Behavior
When exporting to Excel, multi-item cells render each item on a separate line within the same cell. Comma-separated values in the sheet are converted to newline-separated lists in the exported XLSX file.Complete YAML Example
Related Pages
- Columns — base column configuration reference
- Binding Syntax — dot-separated path construction rules
- Sources — data source and expansion path configuration
- Relationships — domain model relationship definitions
- Column Properties — full list of column-level properties
Sources: KB: how-to-add-external-references-column-design-outputs | Tickets: multi-item configuration issues | Code: powersheet.yaml, render-columns.tsx, permissions-levels.template.yaml
Sources
Sources
KB ArticlesSupport TicketsSource Code
powersheet.yamlprod-powersheet-src/com.nextedy.powersheet.client/ltc-repo/packages/sheet/SheetComponent.tsxprod-powersheet-src/com.nextedy.powersheet.client/ltc-repo/packages/sheet/commands/exportXlsx.tsxprod-powersheet-src/com.nextedy.powersheet.client/ltc-repo/packages/common/types/api/document.tsprod-powersheet-src/com.nextedy.powersheet.client/ltc-repo/packages/sheet/render-columns.tsx