> ## Documentation Index
> Fetch the complete documentation index at: https://learn.nextedy.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Configure Multi-Enum Columns
> Set up multi-select enumeration columns in your Nextedy RISKSHEET grid that allow users to choose multiple values from a checkbox dropdown list.
export const LastReviewed = ({date}) => {
if (!date) return null;
const formatted = new Date(`${date}T00:00:00Z`).toLocaleDateString("en-US", {
year: "numeric",
month: "long",
day: "numeric",
timeZone: "UTC"
});
return
Last reviewed on {formatted}
;
};
## Single-Select vs. Multi-Select
The critical distinction between single-select and multi-select enum columns is the column `type` prefix:
| Type Prefix | Behavior | Stored Format |
| -------------------- | -------------------------- | ---------------------- |
| `enum:` | Single value dropdown | Single enum ID string |
| `multiEnum:` | Multi-select checkbox list | Collection of enum IDs |
Using `enum:` for a Polarion field that allows multiple values renders a single-select dropdown even though the underlying field supports multiple values. You must use `multiEnum:` to enable the multi-select picker.
## Where Enum Values Come From
Enumerations in Risksheet are **not** defined inside the sheet configuration. They are managed in Polarion and referenced from the column `type`:
1. An administrator defines the enumeration in **Administration > Enumerations** (project-scoped or global).
2. A custom field on the risk work item type binds to that enumeration (single-value or multi-value).
3. A Risksheet column points at the field via `bindings` and at the enumeration via `type: multiEnum:`.
The server loads enum values automatically — no enum list lives in the sheet configuration file. This keeps the value lists managed where Polarion administrators expect them and avoids duplication across documents and templates.
## Define a Multi-Enum Column
Add a column with the `multiEnum:` type prefix in the sheet configuration (the sheet configuration file, editable through the YAML editor since v25.5.0):
```yaml theme={null}
columns:
- id: allocation
header: Allocation
bindings: allocation
type: multiEnum:allocation_options
```
Key properties:
| Property | Purpose |
| ---------- | ------------------------------------------------------------------------- |
| `id` | Unique column identifier used elsewhere in the configuration |
| `header` | Display text shown in the column header |
| `bindings` | Polarion custom field ID storing the selected enum IDs |
| `type` | `multiEnum:` prefix followed by the enumeration ID configured in Polarion |
The enumeration ID after `multiEnum:` must exactly match the ID of an existing Polarion enumeration. Confirm the correct ID in **Administration > Enumerations** before adding the column.
## Connect to Polarion Multi-Select Fields
For columns bound to Polarion-native multi-select custom fields, the `type` must reference the enumeration that the custom field uses. Verify the enumeration ID in the Polarion custom field definition.
Standard multi-enum field:
```yaml theme={null}
columns:
- id: measures
header: Measures
bindings: measures
type: multiEnum:wit_measure-en_me_allocation
```
WorkItem reference multi-enum (when the picker chooses from work items of a type rather than a flat enum list):
```yaml theme={null}
columns:
- id: workpackages
header: Work Packages
bindings: workpackages
type: multiEnum:@NoIDWorkItems[workpackage]
```
The enumeration identifier must exactly match the definition in Polarion. Open your Polarion administration panel to confirm the correct identifier.
## Multi-Select Display Behavior
The multi-enum editor displays selected values in a compact format:
Up to 2 selected items are shown in the collapsed cell. When more than 2 are selected, the display shows the first items followed by a "+N more" indicator. Multi-enum fields are optional by default and can be left empty.
## Dependent Multi-Enums
Multi-enum columns can be made **dependent** on another column so that the picker only offers values consistent with the parent selection. Dependent enumerations are a column-level feature (v25.3.1+) — configured on the column itself, not in any top-level configuration section. They are typically used to keep large enum lists manageable by filtering options based on context (e.g., showing only software measures when the risk category is "Software").
Consult the dedicated guide for the column-level properties and supported relationship patterns: [Configure Dependent Enums](/risksheet/guides/advanced/dependent-enums).
## Filter Multi-Enum Columns
Multi-enum columns offer two filtering modes with different behavior:
### Filter by Value (Exact Match)
The default "Filter by Value" mode matches exact combinations. If a cell contains both "Hardware" and "Software", selecting only "Hardware" in the filter will **not** match because the exact combination differs.
### Filter by Condition (Partial Match)
To find all rows containing a specific enum value regardless of other selections:
1. Click the column filter icon.
2. Select **Filter by Condition**.
3. Choose **Contains** from the condition dropdown.
4. Enter the enum value to match.
For most use cases, "Filter by Condition" with "Contains" is what users expect. It finds all rows that include the selected value, regardless of other values in the cell.
## Export Behavior
* **Excel export**: Multi-enum IDs are converted to display names and separated by commas.
* **PDF export**: Values render as a comma-separated list of display names.
* **Cell merging**: Multi-enum columns merge when their value arrays are identical (same selected options).
## Verification
After configuring your multi-enum columns, you should now see:
* A checkbox dropdown appearing when you click a multi-enum cell.
* Multiple values selectable simultaneously.
* Selected values displayed as a compact comma-separated list in the cell.
* Dependent filtering narrowing options when a parent column value changes (if the column is configured as dependent).
## See Also
* [Configure Enum Columns](/risksheet/guides/columns/enum-columns) — single-select enum configuration
* [Configure Dependent Enums](/risksheet/guides/advanced/dependent-enums) — cascading enum relationships
* [Configure Multi-Select Enums](/risksheet/guides/advanced/enum-multiselect) — advanced multi-select patterns
* [Apply Conditional Formatting](/risksheet/guides/styling/conditional-formatting) — style cells based on values
* [Add a Basic Column](/risksheet/guides/columns/add-basic-column) — column configuration fundamentals