Table Instance - Capture Rows

The 'Pattern' property defines the core logic for row extraction. It should be a regular expression that matches the text content of each table row. The pattern may include named groups to capture cell values directly.

Configuration

• Enter a regular expression that matches the structure of a single table row.
• Use named groups (e.g., (?<ItemNo>...)) to extract cell values for each column.
• The pattern is applied to the source text, and each match is treated as a row.

Example

To capture invoice line items such as:

Use a pattern like:

Impact

• Changing the pattern alters which rows are captured and how cell values are extracted.
• Incorrect patterns may result in missed rows or invalid data.

Tips

• Test your pattern using sample text and a regex tester.
• Use anchors (^, $) to restrict matches to full lines if needed.
• Combine with 'Prefix' and 'Suffix' for context-sensitive extraction.

The 'Prefix' property allows you to specify a regular expression that must match immediately before each row. This is useful for ensuring that only rows with a specific preceding context are captured, such as a header, section marker, or delimiter.

Configuration

• Enter a regular expression that matches the required prefix for each row.
• The prefix is not included in the captured row, but must be present for a match to occur.

Impact

• Setting a prefix restricts row extraction to matches preceded by the specified pattern.
• Omitting the prefix allows all matches, regardless of context.

Tips

• Use for documents with repeating sections or multiple tables.
• Combine with 'Pattern' and 'Suffix' for precise extraction.

The 'Suffix' property enables you to require a specific pattern immediately following each row. This is useful for capturing rows that are followed by a delimiter, summary line, or other marker.

Configuration

• Enter a regular expression that matches the required suffix for each row.
• The suffix is not included in the captured row, but must be present for a match to occur.

Impact

• Setting a suffix restricts row extraction to matches followed by the specified pattern.
• Omitting the suffix allows all matches, regardless of what follows.

Tips

• Use for tables with summary or footer lines.
• Combine with 'Pattern' and 'Prefix' for context-aware extraction.

The 'Lines Per Row' property controls how rows are grouped when the table structure is strictly fixed. If set, each row will always occupy the specified number of lines. If unset or set to zero, rows are extended down to the next match, allowing for variable-length rows.

Configuration

• Set to a positive integer to enforce a fixed number of lines per row.
• Set to zero or leave unset for variable-length rows.

Example

For a table where each row spans exactly 2 lines:

Set 'Lines Per Row' to 2 to group each pair of lines as a single row.

Impact

• Fixed line count ensures consistent row grouping, even if the pattern matches only part of the row.
• Variable line count extends each row down to the next match, useful for tables with irregular row lengths.

Tips

• Use fixed line count for structured tables with predictable row formats.
• Leave unset for tables with merged, wrapped, or variable-length rows.