Column
Intersection Columns
Keeps only the columns both tables have, dropping everything either one lacks.
When to use it
Use it to cut two differently shaped exports down to the fields they share, ready to compare or stack them.
In a pipeline
File InputIntersection ColumnsMerge Rows
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Rows To Keep | select | — | a |
| Match names ignoring case | checkbox | — | false |
Example
The fields both exports carry
- Rows To Keep=Both tables' rows, stacked
| Pin | Columns |
|---|---|
| A | Id, Name, Region |
| B | Id, Name, Spend |
| Id | Name |
|---|---|
| 1 | Ada |
| 2 | Ben |
With Rows To Keep on Table A's rows, only A's rows come back; stacked, B's rows follow them under the same columns.
Worth knowing
- Columns are matched by name. Tick Match names ignoring case to treat "Email" and "email" as one column; table A's spelling is the one you get back.
- Stacking both tables' rows is the tidy way to combine two exports of different shapes: narrow them to the shared fields here, then use Union Rows if you also want duplicates removed.
- If the tables have no column name in common the result is empty, and the node says so.