v26.03: Working with Transform Nodes
Transform nodes (formerly Calculation nodes) transform data from upstream nodes using various methods.
Available Data Types
Data Type |
Description |
|---|---|
|
v26.03: Mapping |
Transforms data by applying predefined Mapping Tables to input datasets |
|
v26.03: SQL Script |
Provides SQL-based data transformation capabilities |
Aggregate |
Aggregates data based on grouping |
Append |
Appends multiple datasets |
Deduplicate |
Removes duplicate records |
Filter |
Filters data based on conditions |
Join |
Joins multiple input datasets |
Lookup |
Performs lookup operations |
Pivot |
Pivots data structure |
Python Script |
Creates Python-based transformations |
Recipe |
Applies multi-step transformation recipes |
v26.03: Mapping Node
The Mapping node transforms data by applying predefined Mapping Tables to input datasets.
To configure a Mapping node:
Click + Add Node from the Level 2 header. The Add Node dialog opens.
Select Transform from the left panel.
Select Mapping from the right panel. The node appears on the canvas and the configuration side panel opens.
-
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.
-
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.
Mapping nodes support workflow parameter references for dynamic value resolution.
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:
Click + Add Node from the Level 2 header. The Add Node dialog opens.
Select Transform from the left panel.
Select SQL Script from the right panel. The node appears on the canvas and the configuration side panel opens.
-
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.
(Optional) Select Validate to check the syntax before publishing.
-
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 .