> 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/setup/document-types/fuzzy-data-configuration-with-list-of-values.md).

# 使用值列表配置模糊数据

### **概述**

每种文档类型都有自己的值列表 (LoV) 配置，必须分别设置。与**使用主数据配置模糊数据**不同，**值列表**不会提供默认查找组。

### 配置值列表，请导航至：

设置 → 全局设置 → 文档类型 → 发票 → 字段 → 主数据设置 → LOV 主数据

### **创建新的值列表配置**

创建值列表配置有两种方式：

**1. 复制现有查找项**

* 这会复制现有组中的所有信息和字段。
* 您只需提供一个**新名称**。

**2. 从头创建查找项**

* 点击\*\*“创建值列表”\*\*。
* 填写所需信息：
  * **配置名称** → 值列表的名称。
  * **查找表** → 用于检索值的表。
  * **冲突处理器** → 选择一项：
    * 最佳分数
    * 返回空值
    * 返回第一项
  * **上下文类型** → 确定 LoV 应用于**抬头**级别还是**行**级别。
  * **全部匹配** → *(需要更多详细信息)*

### **管理值列表组中的字段**

每个 LoV 组都包含可**添加、移除或编辑**的字段。

**添加新字段**

要在组中添加新字段：

* 在相应组内点击\*\*“创建”\*\*。
* 提供以下信息：
  * **查找字段** → 查找表中的列名。
  * **验证字段** → 对应的 DocBits 字段。
  * **父字段** → *(需要更多详细信息)*
  * **搜索运算符** → 选择一项：
    * 智能
    * 包含
    * 完全匹配
    * 开头为
    * 结尾为
  * **复选框：**
    * **自动触发** → 启用后，如果另一个查找配置中的字段共享同一列，则每当该字段更新时，此字段也会**自动**更新。
    * **可搜索** → 将该字段设为**值列表**字段，以便在查找表中进行搜索。

#### **最后一步：将字段添加到布局**

配置好值列表字段后，**请务必使用布局构建器将其添加到布局中**。如果字段未添加到布局，则无法使用。


---

# 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/setup/document-types/fuzzy-data-configuration-with-list-of-values.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.