2026-06-23 - Union Column Name Matching and Case Preservation Fix¶
Release¶
AgileData.io - Consistent Columns: Union Table Name Matching Now Correct and Case-Preserving
When AgileData combines data from multiple sources using a union rule, column names from each source need to be matched and aligned correctly. Two related bugs were affecting this process: column names weren’t always matched in the right order, and case wasn’t being preserved correctly during the match and alignment step.
The fix sorts table names consistently before passing them through the column name matching logic, ensuring the regexp replace applies in the correct sequence. Case preservation has also been improved so that your original column casing is maintained in the output, rather than being inadvertently changed during the union process.
What was happening:
Table names passed to the column matching logic in inconsistent order, causing incorrect column name alignment in union outputs
Column name casing could be altered during the union column matching step
What this means for you:
Union rules produce correctly named and correctly cased columns in the output
No more subtle column naming discrepancies in unioned datasets
Last Refreshed¶
Doc Refreshed: 2026-06-23