> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/8.5/user-guide/user-interface/menu-bar/edit/operand-types/perform-en-masse-operation.md).

# Perform en masse operation

If you have selected a range before applying an operand conversion command, IDA will display a dialog box.

You can choose a range of operands to perform an en masse operation:

```
 ALL OPERANDS
 -----------
```

The operation will be performed on all operands as a toggle. For example, if you ask to convert to a character, then all non-character operands will become characters, and all character operands will become non-chars.

```
 OPERAND VALUE RANGE
 -------------------
```

The operation will be performed on the [void](/8.5/user-guide/user-interface/menu-bar/search.md#search-for-next-suspicious-operand) operands which contain immediate numbers in the specified range.

```
 ... OPERANDS
 ------------
```

This selection will convert all operands with the specified type to undefined operands. Example: all characters become non-characters.

```
 NOT ... OPERANDS
 ---------------
```

This selection allows to convert all operands that do not have the specified type to the specified type. Example: all non-characters to characters.

```
 NOT TYPED OPERANDS
 -----------------
```

This selection allows to convert all operands without any type to the specified type. Example: all operands with no type to characters.

```
 APPLY ONLY IF POSSIBLE
 ---------------------
```

IDA will check whether an operand can be represented with the specified type (as a character constant, for example), and perform type conversion only if the check is successful.


---

# 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.hex-rays.com/8.5/user-guide/user-interface/menu-bar/edit/operand-types/perform-en-masse-operation.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.
