> 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/editing-and-deleting-columns.md).

# 编辑和删除列

除了标题以外，所有内容都直接在列表中更改；没有编辑对话框。

**位置：** Settings → Global Settings → Document Types → Table Columns

## 切换标记

勾选或取消勾选行中的复选框。更改会立即保存（*Successfully saved*）。

| 标记              | 开启                             | 关闭                          |
| --------------- | ------------------------------ | --------------------------- |
| **Is Required** | 任何行中的该列为空时，审批会被阻止；验证界面会标记该单元格。 | 允许单元格为空。                    |
| **Read Only**   | 显示该值，但无法覆盖输入。适用于来自查找或脚本的值。     | 用户可以编辑该单元格。                 |
| **Hidden**      | 该列会从验证界面和导出结果中消失，但数据会保留。       | 显示并导出该列。                    |
| **Use AI**      | AI 表格提取会填充此列，包括对已训练规则的供应商。     | 由已训练规则填充该列；如果没有规则，则由 AI 填充。 |

{% hint style="info" %}
标记仅对更改后上传或重新启动的文档生效。打开的文档会保留当前表格，直到重新启动。
{% endhint %}

## 重命名标题

点击 *Actions* 列中的翻译图标（*Update translation key*），输入新标签并确认。旁边的信息图标会显示当前生效的标签及其来源。只有标签会更改；技术性的 *Column name* 保持不变，因此脚本、导出映射和已训练规则仍可正常工作。

## 更改类型或表格

无法更改。隐藏该列（如果是组织自建的列，也可以删除），然后添加一个类型正确的新列。

## 删除列

只有组织创建的列才提供删除操作。默认列无法删除，可以将其隐藏。

1. 打开 *Actions* 列中的三点菜单，然后选择 **Delete**。默认列不会显示此选项。
2. 确认。

删除后的影响：

* 该列会从配置中移除。**此后**处理的文档将不再包含该列。
* 已提取的文档会保留该列及其值，直到重新启动。
* 已训练规则中对该列的映射仍会对其他列继续生效；已删除列的映射会被忽略。
* 如果导出映射或脚本引用了该列，请移除相应引用；否则导出或脚本会因找不到列而失败。

## 撤销删除

无法从列表中恢复已删除的列。重新添加同名列即可：技术名称根据标题生成，因此以相同标题创建的列会获得相同的 *Column name*，现有映射也会再次匹配。


---

# 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/editing-and-deleting-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.