> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/merge-duplicate-asset-attribute-options.md).

# Merge duplicate asset attribute options

Combine two saved options on a Dropdown, Multi-select, or Typeahead attribute that mean the same thing, such as `5lb ABC` and `5 lb ABC`.

> **Where to find it:** Settings → Assets & Reports → select an asset type → select an attribute's options

1. Beside the option you want to remove, select **Merge into** and choose the option to keep.
2. The merged option leaves the list, and the option you kept shows what is merging into it. Select **Undo** to put the merged option back.
3. Select **Save**. Assets and inspection-report answers that used the merged option now use the option you kept.

**Merge into** appears only on saved options; save a new option before merging it. While merges are waiting to be saved, you can't change the attribute's type or clear all its options: save or undo the merges first.

When you're changing an attribute's type, **Merge into** is hidden. Use **Map existing values** to combine values instead (see [Map values when changing an asset attribute type](/administration/settings/map-values-when-changing-asset-attribute-types.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://learn.withessential.com/administration/settings/merge-duplicate-asset-attribute-options.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.