Custom File Parsing
Infoveave Data Automation — Format Parsing
Proprietary text file in. Structured table out. Defined by your JSON rules.
Not all data sources produce CSV or Excel files. Legacy ERP systems, government agencies, banking platforms, and logistics providers often deliver data in proprietary flat-file formats — positional layouts, multi-line records, custom separators. Custom File Parsing lets you define the parsing rules in a reusable JSON template file, transforming any consistent text format into a structured table without writing code or building a custom ETL script.
What Custom File Parsing does
Parse non-standard, fixed-structure text files using a JSON template that defines how to extract fields. Handle proprietary legacy formats, EDI-like flat files, and any structured text that CSV parsers cannot handle — without writing code.
When to use Custom File Parsing
- Your data source delivers files in a proprietary or legacy text format that cannot be loaded as a standard CSV
- You receive EDI-like flat files, multi-line records, or files with custom field separators
- A government agency or banking institution delivers reports in a fixed-position layout without column headers
- You need to ingest text files with a consistent structure and want to define the parsing logic once and reuse it across runs
When to avoid it
- Your files are standard CSV or TSV — use Read CSV Files instead, which requires no template
- Your files are Excel spreadsheets — use Read Excel Files
- Your files have fixed-width columns rather than a custom structure — use Fixed Length File Parsing, which is specifically designed for positional formats
Where it fits in your Infoveave automation
Custom File Parsing is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Custom File Parsing
Real scenarios where this transformation saves hours of manual work.
Bank Statement Parsing
A bank delivers account statements in a proprietary multi-line format: one line with the account header, followed by transaction lines, followed by a footer total. A JSON template defines which lines map to which fields, letting the pipeline produce a clean transactions table from each statement file.
SCADA Log Ingestion
Manufacturing equipment produces SCADA logs in a vendor-specific format mixing metadata headers with sensor readings. Custom File Parsing extracts temperature, pressure, and cycle count readings from each log block, feeding the data warehouse for OEE analysis.
Carrier Manifest Processing
A freight carrier delivers daily manifests as a structured text file with a multi-part record per shipment. The JSON parsing template defines segment markers and field positions, converting the manifest into a structured shipment table used for tracking and billing reconciliation.
See Custom File Parsing in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
/templates/manifest_parse_rules.jsonUTF-8\n (newline)10000Input Data
| Raw file content (lines) |
|---|
| HEADER|2026-04-11|BatchID=B9922 |
| REC|10045|Widget A|100|22.50 |
| REC|10046|Widget B|50|18.00 |
| TOTAL|150|4125.00 |
Output Data
| RecordID | Product | Quantity | UnitPrice |
|---|---|---|---|
| 10045 | Widget A | 100 | 22.50 |
| 10046 | Widget B | 50 | 18.00 |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
JSON Template File
Path to the JSON file that defines the parsing rules. The template specifies which lines or sections map to fields and how to extract values. Create one template per file format and reuse it across all runs that use that format.
File Encoding
Character encoding of the source file. Common values: UTF-8, ASCII, ISO-8859-1, Windows-1252. A mismatch will cause garbled characters in the output — check with the file provider if unsure.
Line Separator
The character sequence used to separate lines in the file. Typically newline (\n) for Unix files or carriage return + newline (\r\n) for Windows files.
Max Row Lookup Count
The maximum number of rows the parser will examine when applying the template rules. Default is 10,000. Increase for very large files; reduce for performance optimization on constrained environments.
Frequently asked questions
Everything you need to know about Custom File Parsing in Infoveave.
Also in Format Parsing — and what runs before & after
Transformations in the same family as Custom File Parsing, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Custom File Parsing is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
