> 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/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns.md).

# 表格列

表格列定义文档类型的行项目表包含哪些列：DocBits 会向每列提取什么内容、用户在验证屏幕上看到什么内容，以及导出时发送到 ERP 的内容。

\*\*位置：\*\*设置 → 全局设置 → 文档类型 → 表格列

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-a356b811a06d685716cc788488c20ba5717a7a33%2Ftable-columns_list.png?alt=media" alt="表格列列表，显示每列的“必填”“只读”“隐藏”和“使用 AI”标记"><figcaption><p>表格列：每行对应一列，可直接在列表中切换标记</p></figcaption></figure>

## 您会看到什么

每一行对应一个表格中的一列。列表显示：

| 列         | 含义                                                                    |
| --------- | --------------------------------------------------------------------- |
| **列名称**   | 技术名称，根据标题生成（大写字母，单词之间用下划线分隔）。用于脚本、导出映射和 API。之后无法更改。                   |
| **标题**    | 在验证屏幕上显示的标签。可通过 *操作* 列中的翻译图标（*更新翻译键*）进行更改。                            |
| **列类型**   | `AMOUNT`、`STRING`、`DATE`、`NUMBER`、`BOOLEAN` 或 `CURRENCY`。决定验证和格式设置方式。 |
| **表格名称**  | 此列所属的表格，例如 `INVOICE_TABLE`。                                           |
| **必填**    | 只要任意行中的此列为空，文档就无法获批。                                                  |
| **只读**    | 用户可以看到该值，但无法编辑。                                                       |
| **隐藏**    | 此列既不显示，也不会导出。可用于关闭不需要的默认列。                                            |
| **使用 AI** | 即使供应商已训练规则，AI 表格提取仍会填充此列。                                             |
| **操作**    | 翻译图标：重命名标题。信息图标：显示标签的来源（您的翻译、默认值或键）。三点菜单：*删除*，仅适用于贵组织创建的列；默认列只能隐藏。    |

列表上方有两个按钮：

* **创建新表格**：为文档类型添加第二个行项目表（例如，在项目表旁添加费用表）。
* **添加新表格列**：打开 [添加新列](/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns/adding-a-new-column.md) 中所述的对话框。

## 默认列和自定义列

每种文档类型都自带一组默认列（发票包括：项目编号、描述、数量、单价、总金额、税额等）。这些列属于 DocBits，而非贵组织，因此无法删除；您可以将其隐藏。自行添加的列属于贵组织，可以删除。

{% hint style="info" %}
**更改仅适用于新文档。** 添加、隐藏或删除的列会应用于更改后上传或重新启动的文档。仪表板上已有的文档会保留提取时的表格。重新启动文档以应用新配置。
{% endhint %}

## 相关页面

* [用途和使用方式](/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns/purpose-and-use.md)：表格列会显示在哪里
* [添加新列](/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns/adding-a-new-column.md)
* [编辑和删除列](/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns/editing-and-deleting-columns.md)
* [最佳实践](/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns/best-practices-2.md)
* [故障排除](/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns/troubleshooting-1.md)
* [训练行字段 / 表格训练](/chinese/guan-li-yu-she-zhi/setup/document-training/training-line-fields-table-training.md)：教 DocBits 识别供应商的表格位置
* [AI 表格](/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/ai-table.md)：用户在验证屏幕上看到的内容


---

# 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/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/table-columns.md?ask=<question>&goal=<user_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.
