2.1 Input Data Tool Configuration & Formats

2.1 Input Data Tool Configuration & Formats

Core Certification Focus: The Input Data tool is tested extensively on the Core exam. You must know its supported file types, how configuration options (like Record Limit and Delimiters) alter incoming data, how the "Output File Name as Field" option behaves, and the exact wildcard syntax for ingesting multiple files or Excel sheets simultaneously.

---

1. Tool Overview & Canvas Role

The Input Data tool (located in the green In/Out tool palette) brings external data into an Alteryx workflow. It connects to local files, network shares, spatial layers, relational databases, and cloud data warehouses.

Tool Anchor Mechanics

• Input Anchors: 0 (It is a source tool; nothing connects into its left side).
• Output Anchors: 1 (Labeled with output arrow 1 on the right side, passing records downstream).

+-----------------------------------------------------------------------------+
|                        INPUT DATA TOOL ANCHORS                              |
|                                                                             |
|   (No Input)  --->  [  Input Data  ]  --->  (1 Output Anchor: Output Data)  |
|                            (Green)                                          |
+-----------------------------------------------------------------------------+

---

2. Supported File Formats & Performance

Alteryx Designer natively reads dozens of structured, semi-structured, and spatial formats. Understanding the operational differences between these formats is essential for exam success:

---

3. Configuration Window Properties & Settings

When you drag an Input Data tool onto the canvas, the Configuration window presents essential parameters that control how files are parsed:

+-----------------------------------------------------------------------------+
|                    INPUT DATA CONFIGURATION PANE                            |
+-----------------------------------------------------------------------------+
| 1. Connect a File or Database: [ C:\Data\Sales\Orders_2026.csv            ] |
| --------------------------------------------------------------------------- |
| Configuration Properties:                                                   |
|   Line 1: Record Limit                  [ 100                             ] |
|   Line 2: Search SubDirs                [ [ ]                             ] |
|   Line 3: Output File Name as Field     [ File Name Only                v ] |
|   Line 4: Delimiters                    [ ,                               ] |
|   Line 5: First Row Contains Field Names[ [X]                             ] |
|   Line 6: Start Data on Line            [ 1                               ] |
|   Line 7: Field Length                  [ 254                             ] |
|   Line 8: Code Page                     [ ISO 8859-1 Latin I            v ] |
|   Line 9: Treat Read Errors as Warnings [ [ ]                             ] |
+-----------------------------------------------------------------------------+

Detailed Property Breakdown

1. Record Limit

• Function: Limits the number of records read from the source data stream during workflow execution.
• Behavior: Reads only the first N sequential records (e.g., entering 100 reads rows 1 through 100).
• Exam Note: Setting Record Limit to 0 reads 0 data records but still pulls the column names/metadata. Leaving it blank reads all records. It does not take a random sample; it reads top-down sequentially.

2. Output File Name as Field

• Function: Appends the source file path information as a new column in the output data stream.
• Options:
  • No (Default): No file name column is created.
  • File Name Only: Appends a column containing only the file name and extension (e.g., Orders_2026.csv).
  • Full Path: Appends a column containing the complete folder path, file name, and sheet/table specifier (e.g., C:\Data\Sales\Orders_2026.csv).
• Column Placement: The newly generated field is automatically placed as the last column on the far right of the data table.

3. Delimiters

• Function: Defines the character used to separate fields in delimited text files.
• Common Values: Comma (,), Tab (\t), Pipe (|), Semicolon (;), or \0 (No delimiter — reads the entire line as a single string field).

4. First Row Contains Field Names

• Function: When checked (default), Alteryx treats row 1 of the file as column headers.
• Unchecked Behavior: When unchecked, Alteryx assigns generic field names (Field_1, Field_2, Field_3, etc.) and treats row 1 as the first record of data.

5. Start Data on Line

• Function: Specifies the line number where data records begin.
• Use Case: Commonly used when raw CSV or text files contain metadata titles or blank lines in rows 1–3 before the actual table header begins.

6. Field Length (Flat Files)

• Function: Defines the maximum character length for string fields in delimited files (default is 254 bytes).
• Warning/Trap: If incoming text data in any cell exceeds this length, Alteryx issues a conversion warning and truncates the string to 254 characters unless this limit is manually increased in the configuration pane.

---

4. Multi-File Ingestion via Wildcards

A major capability of the Input Data tool is ingesting multiple files from a folder in a single step using standard wildcard characters.

Wildcard Characters

• Asterisk (*): Matches zero or more characters.
  • Example: C:\Data\Sales_*.csv matches Sales_Q1.csv, Sales_2026.csv, and Sales_.csv.
• Question Mark (?): Matches exactly one single character.
  • Example: C:\Data\Sales_202?.csv matches Sales_2025.csv and Sales_2026.csv, but not Sales_2026_Final.csv.

Excel Sheet Wildcard Syntax

To read all matching Excel workbooks and sheets, Alteryx uses the triple-pipe delimiter (|||):

• C:\Reports\*.xlsx|||Sheet1 → Reads Sheet1 from all .xlsx files in C:\Reports\.
• C:\Reports\2026_Sales.xlsx|||* → Prompts Alteryx to list or process sheets.
• C:\Reports\*.xlsx|||<List of Sheet Names> → Returns a table containing the names of all sheets across the matching workbooks rather than the record data.

The Golden Schema Rule for Wildcards

When using wildcards to read multiple files:

1. All matching files MUST have the exact same schema (identical column names and compatible data types).
2. If File 1 has columns [ID], [Name], [Sales] and File 2 has [ID], [Customer], [Sales], Alteryx will issue a Schema Mismatch Warning.
3. By default, Alteryx will only read the columns that match the schema of the first file encountered, dropping or nulling unmatched fields in subsequent files.

---

5. Common Exam Traps & Best Practices

[!WARNING] Exam Trap: Record Limit vs. Sample Tool A Record Limit set in the Input Data configuration stops reading data at the file reader level. It does not select a random distribution—it pulls the top N records sequentially. If you need a random 10% or the last 100 rows, do not use Record Limit; use the Sample Tool downstream.

[!IMPORTANT] Exam Trap: 254-Byte String Truncation Flat files (CSV/TXT) default to a field length of 254 characters. If your data contains customer comments or long addresses exceeding 254 characters, Alteryx will silently truncate the data and log a warning in the Results window. You must increase the Field Length parameter (e.g., to 5000 or 10000) in the Input Data tool configuration.

[!NOTE] Exam Trap: Output File Name Placement Questions frequently ask where the file name field is located when "Output File Name as Field" is enabled. It is always appended as the last column on the far right, never inserted as the first column.