> 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/settings/global-settings/document-types/fields/master-data-settings.md).

# Master Data Settings

## Overview

In the **Master Data Settings** section of the **Fields** settings for a specific Document Type, you can view and configure master data mappings to fields used in field validation, using data from [**Master Data Lookup**](/administration-and-setup/settings/document-processing/master-data-lookup.md).

These mappings define how master data is applied to individual fields during validation. This page provides a detailed guide on how to configure and manage these mappings.

## **Accessing** Master Data Settings **Settings**

To access the **Master Data Settings** settings:

1. Go to **Settings → Global Settings → Document Types**

   <figure><img src="/files/Z6XXcNUFYg6HofXCPBEm" alt=""><figcaption></figcaption></figure>
2. Select the desired **Document Type** and click on **Fields**.

   <figure><img src="/files/BaGR321S1kVsfBavjsNL" alt=""><figcaption></figcaption></figure>
3. Click on **Master Data Settings**

   <figure><img src="/files/JYpG2lPVuqSY1tCTsh8k" alt=""><figcaption></figcaption></figure>

## Lookup Master Data

In the **Lookup Master Data** section, you can create lookup configs from your master data to use as field mappings during field validation.

### Default Entries

In the **Lookup Master Data** section, certain default entries are provided by **DocBits**. These entries:

* Cannot be edited or deleted
* Can be deactivated if not needed

Default entries are clearly marked with a **Default** tag for easy identification.

<figure><img src="/files/dZ01ye0vwQBTTO4G1nFl" alt=""><figcaption></figcaption></figure>

### **Create Lookup Config**

To create a new lookup config for Master Data:

1. Navigate to the **Lookup Master Data** section.
2. Click **Create Lookup Config** in the top-right corner.

   <figure><img src="/files/urt3DuaGrSzVMdpDqTkT" alt=""><figcaption></figcaption></figure>
3. Configure the following options:
   * **Lookup Name**\
     The name of the lookup config.
   * **Lookup Dataset Name**\
     Select the dataset that should be used for this lookup config.
   * **Conflict Handler**\
     Defines how to resolve conflicts when multiple matches are found:
     * **Best Score** – Uses the entry with the highest matching score.
     * **Return None** – Leaves the field empty if there's a conflict.
     * **Return First** – Uses the first matched value.
   * **Context Type**

     Specifies where in the document the lookup config will be applied. Choose between:

     **HEADER**

     The lookup is used in field validation. Configure the following:

     * **Match All**\
       When enabled, all fields in the lookup config must match during the search by default.

     <figure><img src="/files/zIRyaCLW1xYGhWnA2bLm" alt=""><figcaption></figcaption></figure>

     \
     **LINE**

     The lookup is used within a document table. Configure the following:

     * **Context Detail**\
       Select the specific table to which the lookup should be applied.
     * **Match All**\
       When enabled, all fields in the lookup config must match during the search by default.

     <figure><img src="/files/FlJm6MB2zLKOCLXrw8AW" alt=""><figcaption></figcaption></figure>
4. Click **Save** to create the lookup config.

   <figure><img src="/files/C7MHKU7YSX9v8yG2GbGA" alt=""><figcaption></figcaption></figure>

### Actions on Existing Lookup Config

To manage an existing lookup config, click the three dots in the top-right corner of the configuration you want to modify.

<figure><img src="/files/Qnuf94Q2IqpFwHlQVI3T" alt=""><figcaption></figcaption></figure>

The following actions are available:

* **Activate / Deactivate**\
  Toggle the status of the lookup config.
  * Active configurations are marked with an **Active** tag.
  * Inactive configurations are marked with an **Inactive** tag.
* **Duplicate**\
  After entering a name and clicking **Done**, a copy of the selected lookup config is created.

  <figure><img src="/files/N38i136W1QO51jUp4KhH" alt=""><figcaption></figcaption></figure>
* **Edit/View**\
  Allows you to modify the selected lookup config.\
  After making your changes, click **Save** to apply them.\ <mark style="color:red;">**Note**</mark>: Default lookup configs can only be viewed, not edited. The **Edit** option will be replaced by **View**.
* **Delete**\
  Permanently deletes the selected lookup config after confirmation.\ <mark style="color:red;">**Note**</mark>: Only configurations without the **Default** tag can be deleted.

  <figure><img src="/files/AnMCAE8ILt75JOZGlJGB" alt=""><figcaption></figcaption></figure>

### Create New Field

To add a new field to your lookup config:

1. Open your desired lookup config.
2. Click **Create** in the top-right corner.

   <figure><img src="/files/M85iBGMWTnPC3QmFouDD" alt=""><figcaption></figcaption></figure>
3. Configure the necessary options.
   * **Lookup Field**\
     The field that will be searched within the selected lookup dataset.
   * **Validation Field**\
     The field that will be displayed during field validation.
   * **Parent Field** (optional)\
     This field is used to validate the correctness of the value in the **Validation Field** by ensuring it matches the corresponding parent entry in the lookup dataset.
   * **Search Operator** (optional)\
     Choose how **DocBits** searches for matches in the lookup dataset:
     * **Smart** – *(Default)* Removes whitespaces from the input and searches for a match.
     * **Contains** – Searches for entries that contain the exact term anywhere in the field.
     * **Ends With** – Searches for entries that end with the specified term.
     * **Exact** – Searches for an exact match of the entire value.
     * **Starts With** – Searches for entries that begin with the specified term.
   * **Auto Trigger** (optional)\
     When enabled, DocBits will automatically populate all fields in the lookup config as soon as this field is filled.
   * **Searchable** (optional)\
     When enabled, users can manually search for master data during field validation.

     <figure><img src="/files/bL4lhtqACbScvQXc5ig5" alt=""><figcaption></figcaption></figure>

     <figure><img src="/files/317QwwrfYD4iO7TqPoIm" alt=""><figcaption></figcaption></figure>
4. Click **Save** to create the new field.

   <figure><img src="/files/QamVnGYInDErIhJtOGKv" alt=""><figcaption></figcaption></figure>

### Actions on Existing Field

To manage an existing field, click the three dots in the **Actions** column next to the field you want to modify.

<figure><img src="/files/c3wWoVYOl2xN8REsZUva" alt=""><figcaption></figcaption></figure>

The following actions are available:

* **Edit/View**\
  Allows you to modify the selected field.\
  After making your changes, click **Save** to apply them.\ <mark style="color:red;">**Note**</mark>: Default fields can only be viewed, not edited. In these cases, the **Edit** option will appear as **View**.
* **Delete**\
  Permanently deletes the selected field after confirmation.\ <mark style="color:red;">**Note**</mark>: Only fields without the **Default** tag can be deleted.

  <figure><img src="/files/AnMCAE8ILt75JOZGlJGB" alt=""><figcaption></figcaption></figure>

## LOV Master Data

The **LOV Master Data** section allows you to create dropdown configurations using values from your master data. These dropdowns can be standalone or dependent on other dropdowns, enabling dynamic filtering and cascading selections during field validation.

### Create LOV Lookup Config

A lov lookup config defines how dropdown options are sourced from a master data table and how those values are displayed and populated into document fields.

**To create a new LOV Lookup Config:**

1. Navigate to the **LOV Master Data** section.
2. Click **Create LOV Lookup Config** in the top-right corner.

   <figure><img src="/files/1LucsCz6amtbe4ciYQag" alt=""><figcaption></figcaption></figure>
3. Configure the following options:
   * **Lookup Lov Name**\
     The name of the lov lookup config.
   * **Lookup Lov Dataset Name**\
     Select the master data table that should be used for this lov lookup config.
   * **Context Type**\
     Specifies where in the document the lov lookup config will be applied:

     **HEADER**

     The lov lookup config is used in field validation. Configure the following:

     * **Lookup Label Field**\
       Select the column whose value will be displayed in the dropdown.
     * **Lookup Value Field**\
       Select the column whose value will be stored internally and used for filtering when a selection is made. This value is not displayed to the user.
     * **Out Field**\
       Defines the field in field validation that will receive the selected label from the dropdown.

     <figure><img src="/files/Fx33oaEQzkN34TSNdYfD" alt=""><figcaption></figcaption></figure>

     \
     **LINE**

     The lov lookup config is used within a document table. Configure the following:

     * **Context Detail**\
       Select the specific table where this lov lookup config should be active.
     * **Lookup Label Field**\
       The column whose value will be displayed in the dropdown.
     * **Lookup Value Field**\
       Select the column whose value will be stored internally and used for filtering when a selection is made. This value is not displayed to the user.
     * **Out Field**\
       Specifies the target field in the table where the selected label will be populated.

     <figure><img src="/files/lMX0hB5Rct8crhrZ5ufE" alt=""><figcaption></figcaption></figure>
4. Click **Save** to create the lov lookup configuration.

   <figure><img src="/files/xKLYkZc0AdsLR49zC4mJ" alt=""><figcaption></figcaption></figure>

### Actions on Existing Lookup Config

To manage an existing lov lookup config, click the three dots in the top-right corner of the configuration.

<figure><img src="/files/RPNLfOVQWqZHoiFhhKxH" alt=""><figcaption></figcaption></figure>

**Available Actions:**

* **Activate / Deactivate**\
  Toggle the status of the lov lookup config.
  * **Active** configurations are marked with an **Active** tag.
  * **Inactive** configurations are marked with an **Inactive** tag.
* **Duplicate**\
  After entering a name and clicking **Done**, a copy of the selected lov lookup config is created.

  <figure><img src="/files/wL7h6acbv78oi6Q2HI2o" alt=""><figcaption></figcaption></figure>
* **Edit / View**\
  Modify the selected config. After making changes, click **Save**.
* **Delete**\
  Permanently deletes the config after confirmation.

  <figure><img src="/files/A9qtqldaUqxwk164mWib" alt=""><figcaption></figcaption></figure>

### Create New Field

Within each lov lookup config, you can define additional fields as dropdowns that act as pre-filters for the main lov logic.

These fields are evaluated before the main lov dropdown is loaded. Based on the values selected in these fields, the results of the main lov field are dynamically filtered—enabling dependent dropdowns.\
For example, selecting a country in a pre-filter field can narrow down the city options in the main lov dropdown.

In addition to creating new fields, you can also use existing fields as pre-filters. When configured this way, the selected value in the existing field will filter the main lov dropdown automatically.

**To add a new field:**

1. Open the desired lov lookup config.
2. Click **Create** in the top-right corner.

   <figure><img src="/files/OklcBKjRnS8KpoQsEd8U" alt=""><figcaption></figcaption></figure>
3. Configure the necessary options.

   **Field Configuration Options (applies to both HEADER and LINE contexts):**

   * **Lookup Field**\
     The column to be searched in the selected dataset for dropdown values.
     * **Filter Field**\
       Specifies the field whose value is used to pre-filter the results of the lov lookup config before the main dropdown is populated.
     * **Filter Value** (optional)\
       Add static filters to further narrow down the lookup results.
     * **Required**\
       When enabled, this field must be populated before any dependent dropdowns can be filled.
4. Click **Save** to create the new field.

   <figure><img src="/files/qGwDB3wI65ypGRVakBKH" alt=""><figcaption></figcaption></figure>

### Actions on Existing Field

To manage an existing field within a lov lookup config, click the three dots in the **Actions** column next to the field.

<figure><img src="/files/mJplAmv02PZb9CfZtrMq" alt=""><figcaption></figcaption></figure>

**Available Actions:**

* **Edit**\
  Modify the selected field. After changes, click **Save** to apply.
* **Delete**\
  Permanently removes the field after confirmation.

  <figure><img src="/files/A9qtqldaUqxwk164mWib" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/fields/master-data-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.