> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/fundamentals/faq/automatic-cleanup-of-deactivated-picklist-values.md).

# Automatic Cleanup of Deactivated Picklist Values

#### What is changing in ARM?

ARM now automatically removes references to deactivated picklist values from all impacted Record Types associated with the same Salesforce object.

#### Why is this needed?

When a picklist value is deactivated at the field level, Salesforce removes its availability from associated Record Types. However, Record Type metadata already stored in Git may continue to reference the deactivated value if those Record Types are not included in the commit.

This can result in stale metadata and potential deployment validation issues.

#### How did ARM handle this previously?

Previously, ARM removed the deactivated picklist value only from the Record Types explicitly selected as part of the commit.

Other Record Types under the same object could continue to reference the deactivated value in Git.

#### How does ARM handle this now?

When a picklist value is deactivated, ARM will:

1. Identify the parent object.
2. Scan all Record Types under that object.
3. Identify Record Types referencing the deactivated value.
4. Remove the invalid reference.
5. Automatically include the impacted Record Types in the commit.

#### Do I need to select all impacted Record Types?

No. ARM automatically scans all Record Types under the parent object, regardless of which Record Types you selected for the commit.

#### Will ARM modify unrelated Record Types or metadata?

No. Only Record Types containing references to the deactivated picklist value are updated. Active picklist values and unrelated metadata remain unchanged.

#### What is the benefit?

This enhancement keeps field and Record Type metadata synchronized in Git, reduces stale metadata references and deployment issues, and eliminates the need to manually identify and commit every affected Record Type.


---

# 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://knowledgebase.autorabit.com/fundamentals/faq/automatic-cleanup-of-deactivated-picklist-values.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.