Skip to main content
This page is the exhaustive property reference for column definitions. For binding path syntax details, see Binding Syntax. For column grouping, see Column Groups. For multi-value columns, see Multi-Item Columns.

Column Configuration Hierarchy

diagram
All column types share the same set of properties described in this reference. The binding path (the YAML key) determines which entity and property the column is bound to. Every segment of a navigation path must have a corresponding expand entry in the Sources configuration.

Column Properties Reference


Basic Column Definition

The YAML key under columns: is the binding path — a dot-separated path from the root entity to the target property:
Direct property columns bind to a property on the root entity type defined in the first source.
To display properties from related entities, use a navigation path. Each segment alternates between the navigation property name (the relationship) and the entity type name (from the data model):
Every navigation segment in a column binding must have a corresponding expand entry in the Sources configuration. If you define a column with binding systemRequirements.systemRequirement.designRequirements.designRequirement.title, the sources must expand both systemRequirements and designRequirements:
For the complete binding syntax rules, see Binding Syntax.

Display vs. Render

Powersheet provides two distinct properties for controlling what a column shows. They serve different purposes and should not be confused.

Display Property

The display property controls which property of a referenced entity appears in the cell. It accepts:
  • A property name on the entity object: title, titleOrName, id, severity, or any custom property path
  • A dynamic expression starting with () =>: a JavaScript arrow function that returns the desired display value
For the full reference, see Display Property.

Render Property

The render property references a renderer defined in the renderers section or provides an inline JavaScript expression. The output is display-only HTML and does not affect the data model. This is an important difference from formula, which does affect the data.
Each renderer has access to context:
  • item — the current entity
  • value — the cell value
For the full reference, see Render Property.

Focus and URL Resolution

The hasFocus and hasUrl properties control which column receives keyboard focus and which column displays the external platform link.

Focus Column (hasFocus)

  • Defines the primary focus column for a given entity level. When a new row is created, focus moves to this column.
  • If multiple columns at the same level have hasFocus: true, only the first one found is accepted.
  • If no column has hasFocus, the first column with hasUrl is used as the focus column.
  • If neither hasFocus nor hasUrl is set, the first editable column at that level receives focus.

URL Column (hasUrl)

  • Defines the column that displays a clickable link to the record in Polarion (or other target platform).
  • The link is only displayed if the record has a targetLink defined.
  • Multiple columns can have hasUrl: true to show the link in several places.
  • If no column has hasUrl but a column has hasFocus and is valid, the link appears there instead.
  • If neither is configured, the first valid column for that level displays the link.
Only string and number columns are supported for URL display. Columns with multiLine: true are not supported. Columns with custom rendering also do not show the external link.

Formula Columns

The formula property defines a computed column whose value is calculated from other entity properties. Unlike render, formula values affect the data model and can be saved. A formula must be a valid JavaScript arrow function starting with () =>:
The formula has access to the current entity via context.item. For the full expression reference including the context object, see Dynamic Value Expressions.
formula computes a value that is part of the data and can be saved back. render produces display-only output. Choose formula when the calculated value needs to persist; choose render for presentation-only formatting.

Multi-Item Columns

Setting multiItem: true turns a column into a multi-item picker. This is used for many-to-many relationships where multiple related entities should be displayed and selectable without creating an additional hierarchy level.
Multi-item columns do not support one-to-many relationships at this time. Use navigation path columns with expand to display one-to-many relationships as separate hierarchy levels instead.
For the full reference, see Multi-Item Columns.

Picker Configuration (list)

The list property configures the dropdown picker behavior when a column is bound to a reference (related entity).

Client-Side Filtering (filter)

The filter property defines an initial client-side value filter applied when the sheet loads. Only rows matching the filter values are shown; all other values are hidden.

Interactive sort and filter controls

Beyond the configured initial filter, users can sort and filter any column at runtime. Selecting a column in the work items tree reveals sort arrows and a funnel filter icon next to the column title:
Column header label 'Title' with vertical up/down sort arrows and a funnel filter icon next to it, used to sort or filter that column at runtime
Clicking the funnel opens a filter dialog with two tabs: Value (pick the specific values to keep visible) and Condition (define a filter expression). The dialog supports a search field, Select All, an eraser to clear the filter, and Cancel/Apply buttons.
Filter dialog opened from a column funnel icon, showing Value and Condition tabs, a Search field, Select All checkbox, individual value rows with checkboxes, an eraser clear-filter button, and Cancel/Apply buttons
Once a filter is active, the funnel icon in the column header turns green, and the toolbar shows the filtered row count (e.g. 17 / 54 rows) alongside a global funnel indicator:
Powersheet toolbar showing a 'Use Step' column with sort/filter icons, a green funnel indicating an active filter, and the row count display reading '17 / 54 rows' to confirm how many rows currently match the filter
To remove all active filters at once, use Menu > Filter & Sort > Clear all filters:
Filter & Sort submenu of the Menu dropdown showing the 'Clear all filters' entry, which removes every active column filter in a single click

Row Grouping (groupBy)

The groupBy property enables grouping rows by the column’s values. It supports two forms: Boolean (legacy):
Object with options:
When hideCounter is true, the item count next to each group header is hidden. By default, the group row counter visibility is controlled by the root-level showGroupRowCounter property.

Header Styling

The header property controls the visual appearance of the column header. It references a named style from the styles section.
The header.style value can be shared across columns using YAML anchors:
The headerStyle value from the column’s columnGroup is applied by default and can be overridden by header.style on the individual column. For the full style reference, see Styles.

Frozen Columns

Setting frozen: true freezes the column so it remains visible when scrolling horizontally. If multiple columns have frozen: true, the freeze boundary is placed at the last frozen column — all columns up to and including that column are frozen.

Aggregate Row

The aggregate property defines a calculation displayed in the aggregate (summary) row at the bottom of the sheet.

Column with Formatter

Reference a formatter to apply conditional styling or enforce read-only behavior:
The referenced formatter must be defined in the formatters section:
A column can also reference multiple formatters using an array:
See Formatters for the full formatter reference.

Complete YAML Example

A complete sheet configuration demonstrating the key column properties in a requirements traceability context:
Start with a minimal single-entity configuration (one source, a few direct property columns) and extend gradually. Adding navigation path columns, formatters, and views incrementally makes configuration errors easier to diagnose.

Column Property Categories

diagram

Display Properties

Behavior Properties

Styling Properties

Picker Properties

Example: Simple Column

Example: Navigation Column

Example: Reference Column with Picker

Example: Multi-Item Column


Property Quick Reference

For related configuration sections:
Last modified on July 10, 2026