Grooper Help - Version 25.0
25.0.0017 2,127
  • Overview
  • Help Status

Table Header Instance

Data Instance Grooper.Core

Represents the column or row headers of a Table Instance.

Remarks

The Table Header Instance class models the header row(s) or column(s) of a table detected on a document.
It is used in Grooper to capture and manage the header cells that define the structure and meaning of tabular data, such as column names or row labels.

Role in Grooper

Table Header Instances are created automatically during extraction when a Table Instance is detected by Table Extract Methods such as Tabular Layout, Grid Layout, or AI Table Reader.
Each instance contains one or more child Data Instances representing individual header cells, and maintains a reference to the associated Data Table configuration.

Table Header Instances enable Grooper to map extracted table data to the correct columns or rows, even when header text varies in position, wording, or formatting.

Usage and Configuration

  • Table Header Instances are managed by Grooper’s extraction engine and are not typically created or configured directly by end users.
  • They are visible in the Data Review UI, where users can review the detected headers and their alignment with table data.
  • Advanced users may use Table Header Instances in custom validation, reporting, or export scenarios to leverage header information for data mapping or quality control.

Integration with Other Features

  • Table Header Instances support advanced table extraction features, such as dynamic column mapping, stacked headers, and header adjustment.
  • They are used in validation and review workflows to ensure that table data is correctly associated with its intended columns or rows.
  • The header information can be used in downstream logic, such as conditional exports, data normalization, or advanced reporting.

Best Practices

  • Use Table Header Instances for any scenario where accurate mapping of table data to columns or rows is required.
  • Review the detected headers in the Data Review UI to ensure correct alignment, especially for complex or multi-level headers.
  • Leverage header data for advanced automation, validation, or export scenarios where column or row identity is critical.

Properties

NameTypeDescription
General
Document Reference

See Also

Used By

Notification