July 2026

This article describes the significant feature enhancements in product name and version here v26.07.

Enhancements to Transaction Table Import – Allow Column Selection

Transaction Table import is now faster and more flexible, eliminating common friction points in bulk data entry.

Flexible column mapping via pencil icon

Users no longer need to restart the import if columns are in the wrong order. Click any cell and use the pencil icon to instantly reassign it to a different dimension or metric, saving time and reducing re-import cycles.

Custom Data Start Cell

Files with headers, metadata rows, or leading blank space can now be imported directly without manual cleanup. Define a custom Data Start Cell to skip unwanted rows and columns, cutting file preparation time.

CSV and Excel Import Support

Users can now import both CSV and Excel files interchangeably, eliminating format conversion workflows.

Automatic Duplicate Handling

The import process automatically applies the target table's duplicate-handling strategy (retain last value, aggregate all records, or reject duplicates), ensuring imported records match the table's duplicate policy without manual intervention.

Improved Error Handling and Pane Persistence

Partial imports log as Warning (instead of Fail), preserving error details for faster troubleshooting. The import pane stays open across sessions, allowing users to refine mappings and duplicate settings without losing progress.

For more information, see Transaction Table Import: Allow Column Selection in Transactions – Tables article.

New Transaction Table Node to Write Category

Workflows can now close the complete data loop. Users are no longer limited to writing back to Sheets and Master Data—transaction tables are now a full write destination, enabling complex data pipelines entirely within product name and version here.

Write node and configuration

Users can select any transaction table as a write target and pair it with a compatible data source (SQL, read node, mapping), completing the write-path coverage that was previously only available for Sheets and Master Data.

Intelligent Duplicate Handling Detection

The write node detects the target table's duplicate policy and intelligently constrains available handling options during configuration. When the target allows duplicates, only "Insert all records" is available. When duplicates are disabled, the system offers only the appropriate methods—retain last value, aggregate all records, or reject duplicates—ensuring configuration always matches the target table's policy without user error.

Full Audit Trail for Data Lineage

Write execution now provides complete transparency: an output preview shows the transformed data after duplicate handling is applied, and an audit log records the duplicate-handling method used and row counts for each path (written/skipped/aggregated/rejected), enabling admins to verify data integrity and troubleshoot write operations.

For more information, see Configuring Table Node in Working with Write Nodes article.

Enhancements to File Reader Node

File Reader now provides precise control over where headers and data begin in both Excel and CSV files. Workflow authors can now configure separate positions for headers and data, preventing errors when files have metadata rows or headers in non-standard positions.

Header Start Cell and Data Start Cell configuration

Users no longer need to manually adjust files before importing—the File Reader node now lets you define exactly where the header row and data region start. This eliminates errors from files with leading rows, metadata, or non-standard layouts. The node automatically locks CSV headers to row 1 while keeping data position flexible, and column detection updates whenever you change these positions, ensuring downstream mappings stay in sync.

For more information, see Configuring File Reader Node in Working with Read Nodes article.

Enhancements to File Upload Node: Excel File Support

Users no longer need to convert Excel files to CSV before uploading—the File Upload node now accepts both formats, streamlining file handling and eliminating an extra manual step in the import workflow.

For more information, see Configuring File Upload Node in Working with Read Nodes article.

Enhancements to Workflow: Automatic Termination of Long-Running Jobs

System administrators can configure a job timeout at the Instance Setting level (default: 5 hours) that automatically terminates any workflow execution exceeding this duration, protecting system resources from runaway jobs organization-wide without requiring per-workflow configuration.

Enhancements to Workflow Execution Messages and Metric Audit

Users no longer have to guess what changed in their data. Per-node execution messages show exactly which nodes succeeded or failed, and a new Metric Audit Info section lists every metric that was updated (with row counts), giving users complete visibility into what their workflow did and making debugging failures much faster.

Enhancements to Journals

Bulk journal data entry is now faster and less error-prone. Users can paste or import member IDs directly without facing validation errors or manual re-entry cycles.

Copy-paste member ID resolution

Users can now paste a member ID directly into a journal cell and it instantly resolves on save, cutting data-entry time from several clicks (find member in dropdown) to a single paste-and-save action. The "Invalid Members in Line Items" error no longer appears when using IDs instead of full member names.

Import journal data with member ID resolution

When importing bulk journal data from Excel or CSV, numeric member IDs are now automatically resolved to the correct members, eliminating the frustrating "Invalid Members" validation error that forced re-entry. Numbers stay as numbers (1001000 remains 1001000, not 1,001,000), making imports reliable and fast.

Enhancements to Conversations

Team collaboration now works in any language and with security guardrails. Chart discussions, AI control, and localization make Conversations more powerful and safer for enterprise use.

Localization Support

Global teams can now have discussions in French, German, and other languages. All Conversations UI is translated, enabling non-English speakers to collaborate without language barriers and making Conversations accessible across international teams.

Doc Assist redirection in ISW-integrated workspaces

The Doc Assist floating icon now opens Conversations directly, eliminating confusion between two separate discussion tools and consolidating all team interactions in one place.

AI access control for Lineos Chat

Organizations worried about sensitive data in AI systems can now disable Lineos AI per workspace while keeping team Conversations fully functional. This gives administrators the control to use Conversations in restricted environments without AI exposure.

Opening conversations from chart elements

Users no longer need to switch to cell-level discussions to analyze chart insights. Right-click any chart element to open a thread with automatic context capture (element value or full chart), enabling granular chart-level analysis and discussions without leaving the visual.

For more information, see Conversations.

Decimal Formatting Consistency in Imports

Consistent decimal formatting in import preview

Import previews now display metrics consistently, eliminating the confusing visual where the first row shows one decimal place and subsequent rows show different formatting. This consistency with the actual sheet format gives users confidence that what they see in preview matches what will be imported.

Azure Active Directory Service Principal Authentication for MS SQL Connections

Many organizations secure their MS SQL databases using Azure Active Directory (AAD) Service Principal authentication rather than standard SQL Server credentials. JustPerform now supports AAD Service Principal authentication in addition to the existing SQL Server authentication (username/password).

To enable this, users can leverage the existing Parameters field in the Connections pane, which is already used for OData and SAML configurations, to pass additional JDBC connection parameters. AAD Service Principal authentication can be activated by adding the following parameter:

authentication=ActiveDirectoryServicePrincipal

This enhancement enables more secure MS SQL connections, helping organizations meet higher security standards and compliance requirements.

Expanded Dimension Selection in Auto Mapping Standard Rules

When creating auto mapping standard rules, users can now select from all available sheet dimensions for both Input and Output, rather than being limited to the following three dimensions:

• Audit ID

• Chart of accounts

• Flow list

An Update List option has been added below the Input section, displaying all active dimensions in the sheet for selection. Dimensions selected from the Update List are automatically added to both the Input and Output sections.

This enhancement provides greater flexibility and improved efficiency, enabling the product to handle more complex mapping scenarios.

Currency Conversion Now Triggers On Input Change for Planning Sheets

Previously, setting the currency conversion Action to On–Input Change only worked on consolidation sheets. On planning sheets, this setting had no effect, and users had to run On-Demand conversion manually.

With this release, On–Input Change now works on planning sheets too. When enabled, entering, editing, or clearing a value automatically triggers currency conversion and posts the converted result, without switching settings or running Execute manually.

What's Changed:

The converted value now updates automatically whenever an input changes, across single or multiple rows, on both consolidation and planning sheets. Conversions use the same maintained exchange rates as On-demand and produce identical results. On-demand currency conversion is unchanged and continues to work exactly as before.

System Dimension Members Validation in Journal Import

product name and version here now validates system dimension members when importing journals. If any system dimension data is invalid or does not exist, the import is blocked and an Upload Summary is displayed, explaining the cause of the failure and directing you to the log file for details on the invalid members.

Key Benefits

• Improved Data Integrity

  Ensures only valid dimension data enters the system, reducing the risk of corrupted or inconsistent records.

• Faster Error Detection

  Invalid dimension data is identified immediately during import, allowing users to catch and address errors early.

• Clear Error Guidance

  The Upload Summary explains the failure and directs users to the log file, making it easy to identify and resolve invalid members.

• Prevention of Invalid Imports

  Blocks imports containing invalid dimension data, safeguarding the reliability of your reports.

System Dimensions

The following system dimensions are validated:

• Audit ID

• Flow

• Account

• Scenario

• Currency

• Entity

• Time

• Category

Validation of Group, Time, and Scenario Selection Before Group Consolidation

JustPerform now validates the Scenario, Time, and Groups fields before executing a Group Consolidation action triggered from a Sheet, Task, Form Calculation button, or Save action in Process. If any of these fields is empty or invalid, the action is blocked and the following error message is displayed:

"All selections required. Please select to proceed."

This prevents consolidation from running unintentionally with an incomplete or unintended scope, reducing the risk of incorrect results, data corruption, and the need for costly corrections.

Additionally, the backend will never clear Input Currency (LC) data during any consolidation rule execution, except during validation for Multi-Calculation Tasks triggered from a Task or Calculation button, safeguarding against irreversible data loss.

Resolved Issues in July 2026