View Issue Details

IDProjectCategoryView StatusLast Update
0000041Inlyra StudioTransform Toolspublic2026-09-20 23:46
Reporterinlyradev Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Target Versionv1.1.0 
Summary0000041: Multi-Row Calculation: dynamically apply calculations to all numeric fields
DescriptionAdd a dynamic “All numeric fields” target option to the Multi-Row Calculation tool when using Replace Existing Fields.

Currently, users must select individual fields from a fixed checklist. If additional numeric fields appear in the incoming schema later, the user must reopen the tool and select those fields manually.

The new option should evaluate the incoming schema each time the workflow runs and apply the selected calculation independently to every numeric field. This would be particularly useful for datasets containing a changing number of similarly structured columns, such as contract-month prices.

Proposed field-selection options:

• Selected fields
• All numeric fields

When “All numeric fields” is selected:

• Include Int64, Decimal, and Double fields dynamically at runtime.
• Automatically include compatible numeric fields added in future runs.
• Exclude fields selected under Group By.
• Leave Date, String, and Boolean fields unchanged.
• Apply the calculation independently to each selected field.
• Preserve each field’s original name and data type when replacing it.
• Display an explanation that newly added numeric fields will be included automatically.

Example use case:

A dataset contains one column for each futures contract month. Each contract stops receiving new prices after it expires, and additional contract-month columns are introduced over time. The user selects Fill Forward, Replace Existing Fields, and All Numeric Fields. The node carries each contract’s last known price forward and automatically processes future contract columns without requiring the workflow to be reconfigured.

Acceptance criteria:

1. “All numeric fields” is available with Replace Existing Fields.
2. The selection is stored as a dynamic rule rather than a fixed list of field names.
3. New numeric input fields are included automatically during future executions.
4. Group By fields are excluded from replacement.
5. Each numeric field is calculated independently.
6. Existing workflows using individually selected fields remain backward compatible.
7. Schema preview and execution produce consistent results.
TagsNo tags attached.
Report TypeEnhancement
EditionBoth
Operating SystemWindows 11

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-09-20 23:46 inlyradev New Issue