v26.03: Working with Transform Nodes

Transform nodes (formerly Calculation nodes) transform data from upstream nodes using various methods.

Available Data Types

v26.03: Mapping Node

The Mapping node transforms data by applying predefined Mapping Tables to input datasets.

To configure a Mapping node:

1. Click + Add Node from the Level 2 header. The Add Node dialog opens.

2. Select Transform from the left panel.

3. Select Mapping from the right panel. The node appears on the canvas and the configuration side panel opens.

4. Fill in the required fields from the configuration panel:

   Parameter	Description
   Name	Unique identifier. Defaults to Mapping_[n].
   Input	Select an upstream Read or SQL Script node.
   Steps	Select + Add Step to create mappings. Each step requires the following: Step Name (identifier) Mapping Table (the predefined Mapping Table to apply) Source Field Mapping (the source fields to map)
   v26.05:  Settings (Optional)	Configure Precedent and Subsequent nodes to control node execution order. See Working with Node Settings for more details.

5. Select Publish in the Level 2 header to save the configuration.

   After publishing, the following controls become available in the Level 2 header:

   • Refresh: Reloads the grid to reflect changes.

   • Run: Executes the query when valid.

Go to the Execution Output tab to preview the Mapping Table data. The Execution Output tab also displays a real-time data simulation preview: mapped rows show the mapped value, failed rows show N/A, and unmapped rows are blank when Fail on Unmapped Source is not enabled.

v26.04: Users can reorder, edit, and delete steps via the ellipsis menu. Unmapped Handling inherits the "Fail on Unmapped Source" setting from the selected Mapping Table.

v26.03: SQL Script Node

The SQL Script node provides SQL-based data transformation capabilities.

To configure a SQL Script node:

1. Click + Add Node from the Level 2 header. The Add Node dialog opens.

2. Select Transform from the left panel.

3. Select SQL Script from the right panel. The node appears on the canvas and the configuration side panel opens.

4. Fill in the required fields from the configuration panel:

   Parameter	Description
   Name	Unique identifier. Defaults to SQL Script_[n].
   Input	Select + Add to choose upstream nodes. Multiple inputs are supported.
   Query	Enter SQL logic. Select Expand to open the Advanced View for editing.
   v26.05:  Settings (Optional)	Configure Precedent and Subsequent nodes to control node execution order. See Working with Node Settings for more details.

5. (Optional) Select Validate to check the syntax before publishing.

6. Select Publish in the Level 2 header to save the configuration.

   Note: Nodes can be published with invalid queries — a warning icon is displayed in that case.

   After publishing, additional controls become available in the Level 2 header:

   • Refresh: Reloads the grid to reflect changes.

   • Run: Executes the query when valid.

The Query field supports the following:

• Query syntax — {{node_name}} and ${dimension_description} with examples.

• Supported SQL operations — SELECT, JOIN, WHERE, GROUP BY, ORDER BY, functions.

• Validation info — Select Validate to check the syntax before publishing.\

Note: Nodes can be published with invalid queries (warning icon shows)

v26.02: The query is validated on publish or refresh. The system displays a warning icon when SQL queries access unauthorized components.

v26.04: Query syntax: Use {{node_name}} for input nodes, {{node_name}}.DIM_NAME for dimensions .

v26.08: Input Validation and Security

SQL queries can now only reference tables explicitly added as Input nodes (via Read nodes, Master Data, or Preferences).

Direct backend table IDs or names are blocked at both save and execution time.

This closes a loophole where workflows could bypass workspace-level data access controls, ensuring all SQL Script nodes respect workspace-level security policies.

v26.09: SQL Syntax Standardization

The SQL Script node now uses a standardized syntax for referencing nodes, columns, and parameters. This replaces the previous {{node_name}} and ${Node Name} forms.

Node and Column References

Columns are referenced using the format 'node_id'.'column_id', with both the node ID and column ID in single quotes.

• A reference must always include both the node ID and the column ID, dot-separated. A query using a bare column name without a node reference is rejected with a clear error message.

• A single-quoted node or column ID that does not resolve to a declared input node or one of its columns is rejected with a clear error identifying the unknown identifier.

• Single and double quotes are not mixed.

The standardized syntax applies consistently across query writing, the Input/Output structure display, and the data preview. The structure display shows ID (description) while the query uses 'node_id'.'column_id'.

Parameter References

All parameters are referenced using the format $'parameter_name'. The previous ${Node Name} form is no longer used or displayed anywhere.

This applies to every parameter in the Available Parameters panel, including system parameters (Execution Date, Execution Period, Execution User) and user-defined parameters.

Editor Behavior

• Clicking a parameter in the Available Parameters panel inserts it at the cursor position in the $'parameter_name' syntax, rather than copying to the clipboard.

• While typing inside single quotes, the editor suggests matching input node IDs. After 'node_id'., it suggests that node's column IDs, drawn only from the SQL node's declared input nodes. Selecting a suggestion inserts the full 'node_id'.'column_id' reference.

Impact on Existing Workflows

Existing workflows are not upgraded automatically. Existing SQL queries written in the previous syntax — using {{node_name}}.column_name or ${Node Name} — will not run until updated to the new syntax. Any node whose query no longer resolves is flagged as invalid.

Note: Existing nodes keep their current names and IDs. No table is recreated and no ID is changed by this update.