> 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/fields/configuring-field-properties-1.md).

# 配置字段属性

使用 **设置 → 文档类型 → 字段** 控制某个文档类型的字段行为。请先选择文档类型；下方示例显示的是英文界面中的 **Invoice**。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-3eee090d25fd183ab7958ab5c1fdd8c5400a6d06%2Fdbdc155-field-properties-overview-en.png?alt=media" alt="英文 Invoice 字段设置，包含识别阈值、搜索、字段属性列和 Save Settings"><figcaption><p>DocBits 沙盒组织中的 Invoice 字段设置。</p></figcaption></figure>

## 查找字段并更改其属性

1. 在 **Search by Name** 中输入字段名称或标签。此操作会筛选列表，不会更改字段。
2. 找到字段所在行。例如，**Invoice number** 的技术名称为 `invoice_id`。
3. 调整该行中的控件，然后选择 **Save Settings**。表格上方和下方均提供相同的保存按钮。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-9a345f19ca91e9d6959233bdbbd54872ec2e8f33%2Fdbdc155-field-properties-filtered-en.png?alt=media" alt="英文 Invoice number 字段，显示 Required、Read Only、Hidden、Force Validation、Use AI、OCR 和 Match Score 控件"><figcaption><p>搜索 `invoice_id` 后显示的 Invoice number 行。</p></figcaption></figure>

| 控件                   | 用途                                  |
| -------------------- | ----------------------------------- |
| **Required**         | 将验证时必须填写的信息标记为必填。更改此设置后，请检查文档的验证结果。 |
| **Read Only**        | 显示字段，但不允许用户编辑其值。                    |
| **Hidden**           | 在常规文档视图中隐藏该字段。                      |
| **Force Validation** | 要求字段通过验证。请另行配置详细规则；此复选框不是规则编辑器。     |
| **Use AI**           | 请求或停止对该字段进行 AI 提取。该行会显示是否已请求提取。     |
| **OCR**              | 输入字段的 OCR 置信度阈值。这是一个数值，不是开关或语言设置。   |
| **Match Score**      | 输入字段的匹配阈值。这是一个数值，不是开关。              |

**Recognition Settings** 下的 **OCR** 和 **Match Score** 滑块会将相应的值应用到整个字段列表。列标题正下方的复选框会将 **Required**、**Read Only**、**Hidden** 或 **Force Validation** 应用到整个列表。选择 **Save Settings** 前，请检查受影响的行。**Restore Defaults** 会重置字段配置；只有在确实要替换自己的更改时才使用此选项。

## 此视图中的其他控件

* **Create new group** 和 **Create field** 分别用于添加分组或字段。请参阅[添加和编辑字段](/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/fields/adding-and-editing-fields.md)。
* **Master Data Settings** 会打开[主数据配置](/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/fields/master-data-settings.md)。
* 最左侧的复选框用于选择字段。相邻菜单中的 **Reassign Field Group** 可用于重新分配所选字段的分组。
* **Formula** 加号按钮会打开该字段的公式编辑器。**info** 图标会显示字段信息。标准字段无法使用删除图标。

有关验证和匹配的更多信息，请参阅[设置验证和匹配分数](/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/fields/setting-validation-and-match-score.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/fields/configuring-field-properties-1.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.