> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Asset Linking Configurations

> Configure field mapping and custom matching rules

In AssetOps, you match discovered assets against existing ones so each asset appears only once per building. This prevents duplicate or conflicting entries and keeps the asset database consistent.

## Field Mapping

Field mapping determines which data source takes priority when two assets represent the same physical equipment but originate from different data sources.

You maintain an ordered list of data sources for each asset information field, with the top entry representing the highest-priority source. You can reorder the list to change priorities as needed.

```mermaid actions={false} theme={null}
---
config:
  theme: neutral
---
flowchart LR
 subgraph s1["Asset Info Fields"]
        F3["Filed 1"]
        F4["Filed 2"]
        F5["Field 3"]
  end
 subgraph s2["Data Sources"]
        D1["<b>Data Source 1</b>*"]
        D2["Data Source 2"]
        D3["Data Source 3"]
  end
    F1["Field Mapping"] --- F2["Asset Information Fields"]
    F2 --- F3 & F4 & F5
    F4 -- prioritized data source --- D1
    F4 --- D2 & D3

     F3:::Sky
     F4:::Sky
     F5:::Sky
     D1:::Rose
     D2:::Rose
     D3:::Rose
    classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
    classDef Rose stroke-width:1px, stroke-dasharray:none, stroke:#FF5978, fill:#FFDFE5, color:#8E2236
    linkStyle 0 stroke:#00C853,fill:none
    linkStyle 1 stroke:#00C853,fill:none
    linkStyle 2 stroke:#00C853,fill:none
    linkStyle 3 stroke:#00C853,fill:none
    linkStyle 4 stroke:#FF6D00,fill:none
    linkStyle 5 stroke:transparent,fill:none
    linkStyle 6 stroke:transparent
```

## Matching Rules

Matching rules define the [logic behind asset linking](/products/assetops/assets/asset-linking) and determine how discovered assets are compared and matched to existing assets.

Each rule can have up to three conditions. Rule conditions combine an asset field with a match type, which defines how values are compared across different data sources.

```mermaid actions={false} theme={null}
---
config:
  theme: neutral
---
flowchart LR
 subgraph s1["Condition 1"]
        Field1["Field"]
        Match1["Match Type"]
  end
 subgraph s2["Condition 1"]
        Field2["Field"]
        Match2["Match Type"]
  end
 subgraph s3["Condition 3"]
        Field3["Field"]
        Match3["Match Type"]
  end
    Field1 --- Match1
    Field2 --- Match2
    Field3 --- Match3
    A["Matching Rules"] -- access ----- B["Rule 1"]
    B -- rule condition ---- s1 & s2 & s3

     Field1:::Rose
     Field2:::Rose
     Field3:::Rose
     B:::Sky
    classDef Sky stroke-width:1px, stroke-dasharray:none, stroke:#374D7C, fill:#E2EBFF, color:#374D7C
    classDef Rose stroke-width:1px, stroke-dasharray:none, stroke:#FF5978, fill:#FFDFE5, color:#8E2236
    linkStyle 3 stroke:#00C853,fill:none
    linkStyle 4 stroke:#FF6D00,fill:none
    linkStyle 5 stroke:#FF6D00,fill:none
    linkStyle 6 stroke:#FF6D00,fill:none
```