Join files (2) block

❗️
This block will be deprecated in future releases.

The two_join block merges two source files into a single output file based on specified join conditions and matching headers. It acts as a transformation block in a Connect+ dataflow, enabling you to combine data from two separate files using SQL-style join operations before passing the merged output to downstream blocks.

When to use this block

Use this block when your dataflow needs to combine data from two separate files for example, merging bill-level and line-level transaction files before ingestion.

Prerequisites

Before configuring this block, make sure you have:

Two source files with a common column to join on
Regex patterns that uniquely identify each file
Column header names used for joining in each file

Configuration fields

Field name	Required	Description
Block name	Yes	A name for the block instance. The name must be alphanumeric. There is no character limit.
Files 1-2 Join Type	Yes	The type of SQL join used to merge the two files. Select `LEFT_OUTER_JOIN`, `OUTER_JOIN`, `INNER_JOIN`, or `RIGHT_OUTER_JOIN` from the dropdown. Default value: `LEFT_OUTER_JOIN`.
All Files Delimiter	Yes	The delimiter used to separate fields in the source files. For example, `,`.
File 1 Regex	Yes	The filename pattern used to identify File 1. For example, `BILL_LEVEL_MERGE.*.csv`.
File 1 Headers	Yes	The column header name in File 1 used for the join comparison. To match on multiple headers, enter the header names separated by a comma. For example, `BillNumber`.
File 2 Regex	Yes	The filename pattern used to identify File 2. For example, `LINE_LEVEL_MERGE.*.csv`.
File 2 Headers	Yes	The column header name in File 2 used for the join comparison. To match on multiple headers, enter the header names separated by a comma. For example, `BillNumber`.
Output Filename	Yes	The name of the merged output file. For example, `merged_output.csv`.
File Join Use Case	No	The use case for the file join. Select `NONE` or `TRANSACTION_LINE_ITEM` from the dropdown. Default value: `NONE`.
Use Alphabetical Sort	No	Determines whether files are sorted in alphanumerical order before merging. Select `true` or `false` from the dropdown. Default value: `false`.
Merge based on common Name	No	Determines whether files are identified and merged based on a common name pattern. Select `true` or `false` from the dropdown. Default value: `false`.
Merge based on common Name Template File One	No	The filename template for File 1 using the `<common>` tag to identify the common part of the filename. Select `TRANSACTION_LINE_ITEM` or `NONE` from the dropdown. For example, `TktDocument_<common>.dat`.
Merge based on common Name Template File Two	No	The filename template for File 2 using the `<common>` tag to identify the common part of the filename. For example, `TktDocument_<common>.dat`.
File One is Headerless	No	Indicates whether File 1 does not contain column headers. Select `true` or `false` from the dropdown. Default value: `false`.
File two is Headerless	No	Indicates whether File 2 does not contain column headers. Select `true` or `false` from the dropdown. Default value: `false`.
File One Mention Header names (for use in mapping and expressions)	No	The column header names for File 1, separated by commas. Required if File 1 is headerless. For example, `BillNumber,Amount,Date`.
File Two Mention Header names (for use in mapping and expressions)	No	The column header names for File 2, separated by commas. Required if File 2 is headerless. For example, `BillNumber,ItemCode,Quantity`.
Match All Regex	No	Determines whether only the files matching the regex pattern are retained on the server and non-matching files are deleted. Select `true` or `false` from the dropdown. Default value: `false`.
All Unique Match	No	Determines whether duplicate files are identified and deleted. Select `true` or `false` from the dropdown. Default value: `false`.