Text Document - Split

Use this property to ignore header or metadata lines at the start of the file.

• Set to the number of lines to skip before splitting begins.
• Skipped lines are not included in any child document.

If set to a value greater than zero, the document will be split into child documents containing this many lines each.

• Use for fixed-size splitting when content-based splitting is not required.
• If both LinesPerDocument and StartTag are set, a split occurs when either condition is met.

Can be one of the following types:

Assign a Value Extractor that produces a hit on the starting line of a new document.

• The extractor is evaluated on each line.
• When a match is found, a split occurs (optionally offset by StartOffset).
• Use for content-based splitting, such as detecting record headers or section breaks.
• If not set, splitting is controlled by LinesPerDocument only.

• Set to 1 to split on the line immediately above the detected Start Tag, 2 for two lines above, etc.
• Useful when the Start Tag is not on the first line of a logical document.
• Only applies when StartTag is set.

Can be one of the following types:

Assign a Value Extractor to exclude regions of the text document from splitting.

• When a match is found, the current line and all subsequent lines are ignored until the next Start Tag.
• Use to skip over irrelevant or non-data sections.

• Set this property to classify each child document created by the split.
• If not set, child documents will not be classified.
• Use to enable downstream extraction and export workflows.

Can be one of the following types:

• Select the character encoding used by the input file (e.g., UTF-8, Unicode).
• Ensures correct reading of text content, especially for non-ASCII files.
• Defaults to UTF-8 if not specified.

• Enable to automatically detect BOM and adjust encoding as needed.
• Recommended for files that may include BOM, such as those saved from Windows editors.