September 2026

This article describes the significant feature enhancements in JustPerform v26.09.

Enhancements to Transaction Table: Display Properties Preference for Metrics and Local Dimensions

The Transaction Table now displays correct property values in Display Properties columns for metrics and local dimensions. Previously, columns added through Display Properties repeated the transaction amount instead of the actual property value. Each selected property now appears as a separate read-only column named <metric/dimension> - <property> (for example, Revenue - Metrics Type or Department - Data Type), showing the value from the metric or dimension definition. Values are consistent across all rows and are not affected by changes to transaction data. Display Properties columns are excluded from import and row insert operations and are included when the table is exported.

For more information, see the Transactions – Table article.

Enhancements to Workflow: Stable Node and Column IDs

Each data node in a workflow now generates an immutable node ID and an immutable column ID for every output column at the time of creation. IDs are derived from the node and column names and are retained even if the node name or source metric name changes later. The Output section of every Read and Transform node displays columns in the format ID (description). Downstream SQL, Mapping, and Write nodes reference columns by ID, ensuring that metric renames in the source do not break existing node references and that workflows promoted between environments continue to resolve correctly.

For more information, see the Node and Column IDs section in Understanding Node Categories and Types article.

Enhancements to Workflow: SQL Syntax Standardization

The SQL node now uses a standardized syntax for referencing nodes, columns, and parameters. Columns are referenced as 'node_id'.'column_id' with both IDs in single quotes; bare column names are rejected. Parameters are referenced as $'parameter_name'; the previous ${Node Name} syntax is no longer supported. Clicking a parameter in the Available Parameters panel inserts it at the cursor position. The editor provides autocomplete for node IDs and column IDs drawn from the SQL node's declared inputs. Existing SQL queries written in the previous syntax must be updated manually; affected nodes are flagged as invalid until updated.

For more information, see Configuring SQL Node in the Working with Transform Nodes article.

Enhancements to Workflow: Master Data Read Node

A new Read Master Data node is now available on the Workflow canvas. It reads dimension member data as a structured table, making master data available as input to downstream SQL, Mapping, and Write nodes. Authors select a source dimension from a searchable dropdown; the Layout defaults to ID and Description, with additional properties available to add as needed. The node supports localization: authors can add language-specific columns for eligible properties, accessible to downstream nodes by a language-qualified technical ID (for example, description_french). Layout changes are previewed using Refresh Output and take effect only after Publish.

For more information, see Configuring Master Data Read Node in the Working with Read Nodes article.

Enhancements to Dataflow: Mapping Table Management

Mapping tables created in dataflows are now visible and manageable from the Object List. A Mapping Tables folder lists all tables organized by dimension; clicking a table opens its detail pane for viewing and editing. A Delete option is available in the More menu and is permitted only when the table is not referenced by any model enrichment rule or dataflow. Duplicate enrichment rule names are now blocked globally at creation and rename; existing workflows with legacy duplicate names are not affected.

Enhancements to Workflow: DataForge Optimization

This release optimizes Read, Transform, and Write node execution for improved performance and reliability at scale:

• Workflows that previously timed out or failed on large datasets — such as those with 50,000 or more rows — now process reliably up to millions of records.

• The Execution Output preview across all workflow nodes is capped at 1,000 rows. When the dataset exceeds this limit, a message indicates how many records are being shown. Full execution continues to process all records.

Note: All existing node capabilities and behaviors are unchanged.

Select All option for quick batch deletion

The Member Selector dialog for dimensions now includes a Select All checkbox at the top of the members list in the right pane. This lets you quickly select all members with a single click, saving you time when you want to remove them all.

Excel add-in enhancements

Error message when start cell cannot render report

When a user opens a snippet/report in the Excel add-in and the designated start cell doesn't support rendering, an error message appears under the Start Cell option instructing the user to select a supported cell instead. The report renders once the user chooses a valid location.

Out-of-range metric alerts

Previously, when entering data in the Excel Add-in, values outside a metric configured validation range were silently rejected, the add-in showed a generic "data saved successfully" message with no indication that some entries hadn't been saved.

The Excel Add-in now displays the same custom validation message configured for the metric on the web when an out-of-range value is entered. Valid entries are saved as expected. Invalid entries are discarded, and the cell reverts to its previous value (or empty, if it had none). This brings Excel Add-in behavior fully in line with the web experience.