> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/setup/document-training/training-line-fields-table-training/defining-tables-and-columns.md). # Defining Tables and Columns If a table is not recognized completely, use table training to define its area and columns. These examples use a fictional invoice. The illustrated training areas are unsaved drafts. ## Open table training Open the document in **Field Validation**, then open **Table Extraction**. The document appears on the left and the training controls on the right.

English interface for defining tables and columns.

## Enable training mode Turn on **Training Mode** to make the table-selection and column tools available.

Table training with training mode enabled.

The toolbar includes automatic table detection. Check its result against the document before defining columns. This image shows the available tools; it does not demonstrate a completed automatic detection.

Table-training tools including automatic detection.

## Select the table area For a manual selection, choose the pencil tool and drag a rectangle around the column headings and line items. Exclude totals below the table.

Unsaved table area around the fictional invoice's line items.

## Position the column separators Choose the column tool, then place or drag vertical separators between the actual columns.

Table area in edit mode with vertical column separators.

Check the separation of item, description, quantity, unit price and amount. The separators in this example follow the five columns of the invoice.

Table area with column separators positioned for the training draft.

Review the complete area and column assignments before using **Save** or **Save Rules**.

Table area and column separators in an unsaved training draft.

## Check the extracted values Compare the extracted line items with the original document. This image shows the example invoice's already automatically extracted rows in validation. They are not a result of the unsaved training draft above.

Automatically extracted line items of the fictional invoice in validation.

Use **Save Rules** when you intend to retain the training, then test it with further documents from the same supplier. One example does not establish reliable extraction for other layouts. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docbits.com/administration-and-setup/setup/document-training/training-line-fields-table-training/defining-tables-and-columns.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.