Column Type Syntax
| Syntax | Description |
|---|---|
multiEnum:EnumID | Multi-select dropdown using the specified enumeration definition |
Column Properties
| Name | Type | Default | Description |
|---|---|---|---|
id | string | Auto-generated from header or binding | Unique identifier for the column |
type | string | Auto-detected from binding | Must be multiEnum:EnumID for multi-select behavior |
header | string | None | Display text in the column header |
binding | string | Same as id | The Polarion field ID this column maps to |
readOnly | boolean | false | Controls whether the column cells can be edited |
filterable | boolean | true | Controls whether users can filter by values in this column |
width | number | See application | Column width in pixels |
minWidth | number | See application | Minimum resize width in pixels |
level | number | 1 | Hierarchical level at which this column appears (not set for task columns) |
multiLine | boolean | true | Enables multi-line display within cells |
wordWrap | boolean | true | Controls whether text wraps within cells |
headerGroup | string | None | Header group this column belongs to for multi-level headers |
collapseTo | string | None | Column ID to collapse into when header group is collapsed |
cellCss | string | None | CSS class name(s) to apply to cells in this column |
cellRenderer | string | None | Name of a custom cell decorator function for this column |
format | string | None | Display format string for the column data |
Enumeration Definition
Multi-enum columns reference enumeration definitions from theenums section of risksheet.json. Each enum entry is an array of option objects:
Enum Option Properties
| Property | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Internal identifier used for storage, comparison, and cell decorator logic. This is the value stored in the Polarion field. |
name | string | Yes | Display label shown in the dropdown picker and rendered in the cell |
description | string | No | Extended description text (shown in rating: type columns; not displayed in standard enum: or multiEnum: columns) |
icon | string | No | Icon identifier for visual display alongside the option |
Cell decorators, formulas, and filter comparisons always work with enum IDs, not display names. For example, if an option displays as “High” but has
id: "high", use 'high' in your decorator or formula logic.Data Storage
Multi-enum columns support two Polarion storage formats:| Storage Type | Format | Description |
|---|---|---|
| Native multi-enum | Polarion List<IEnumOption> | Native Polarion multi-select custom fields containing IEnumOption objects |
| Comma-separated string | "val1,val2,val3" | String fields containing comma-separated enum IDs |
Rendering Behavior
Multi-enum values render as a list of styled tags within the cell:- Each selected value appears as an individual
span.multi-enum-itemelement - All items are wrapped in a
span.multi-enum-listcontainer - Tags display the
nameproperty from the matching enum definition - If an enum option ID is not found in the configuration, the raw ID value is displayed as a fallback
- Values stored as arrays are processed during cell rendering to resolve IDs to display labels
Filtering Behavior
Multi-enum columns support two filter modes with significantly different behavior:| Filter Mode | Behavior | Use Case |
|---|---|---|
| Filter by Value | Matches exact combinations of selected values | Finding rows with a specific set of selections (e.g., exactly “Safety” and “Regulatory” with no other selections) |
Filter by Condition with Contains | Finds all rows where the specified value is included, regardless of other selections | Finding all rows that include “Safety” among their selections, regardless of what else is selected |
Cell Merging
Multi-enum values participate in the hierarchical merging system. Cells with identical selections merge vertically when they are in the same level group:- Multi-enum values are converted to string representations for merge comparison
- Cells with identical numeric value arrays (same selected options in the same order) merge properly
- Empty brackets
[]or invalid JSON prevent merging - The values must be in identical order for cells to merge
Export Behavior
Excel Export
When exporting to Excel, multi-enum columns are converted to a comma-separated list of human-readable option names:- Internal enum IDs are resolved to display names using the
enumsconfiguration - Values are separated by comma and newline characters
- Unknown enum IDs (not found in configuration) are preserved as-is in the export
PDF Export
PDF export renders multi-enum values as comma-separated text of resolved enum labels, consistent with the Excel export format.WorkItem Enum Fields
For custom fields that are enumerations of WorkItem type, thetype property must match the XML custom field configuration exactly:
WorkItem enum fields require specific type syntax matching the XML custom field definition in Polarion. The exact format depends on your project’s custom field configuration. Check
.polarion/documents/fields/custom-fields.xml for the correct type string. Upstream and downstream WorkItem enum fields have more limited support compared to row item properties.Dependent Multi-Enum Options
Multi-enum editors support dependent option filtering based on a parent enum value. Configure dependencies using therelations section of risksheet.json:
Dependent enumeration support for multi-value enums was added in version 25.4.0. Single-value dependent enums were introduced in version 25.3.1. Ensure your Risksheet version supports the dependent enum feature before configuring
relations.Undo/Redo Support
Multi-enum fields have specialized undo logic. When you undo changes to a multi-enum column, the system restores visible options from stored enum item IDs. Dependent column values are also automatically restored to maintain data consistency.Version History
| Version | Change |
|---|---|
| 24.2.0 | Fix for multiEnum type column behavior |
| 24.6.0 | Fixed multiEnum display at minimal row height; fixed cross-project downstream item linking (previously required removing task.project column as workaround) |
| 25.3.1 | Dependent enum support for single-value enums via relations configuration |
| 25.4.0 | Dependent enum support for multi-value enums via relations configuration |
Error Messages
| Error | Cause | Resolution |
|---|---|---|
| ”Error while loading enums” | Enum configuration references an enum ID that does not exist or cannot be loaded from Polarion | Verify that the enum ID in the type property matches an entry in the enums section or a valid Polarion enumeration |
Complete Example
An FMEA configuration with multi-enum columns for impact categories and affected systems, including dependent enums and cell decorators:Related Pages
- Enum Columns — Single-select enumeration columns
- Column Type Reference — Overview of all column types
- Data Types — Work item type configuration
- Cell Decorators — Conditional formatting with decorators
- Conditional Formatting — All formatting approaches
- Risksheet.json Format — Complete configuration file reference
Sources
Sources
KB Articles
- Enable editing of read-only up-stream columns
- Configure upstream column to show multiple linked work items
GetSetUtil.javaAppConfig.tsExportToExcel.tsRisksheetViewServlet.javaCustomMergeManager.ts