> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/features-in-element-repository/element-identifier-order/reorder-element-and-element-properties-in-repository.md).

# Reordering Element Identifiers

Element identifiers help Avo Assure locate UI elements during test execution. Setting the correct identifier order improves element recognition and increases execution reliability. This article explains how to reorder identifier priority using available options in the Element Repository.

## Reordering Element Identifiers for Multiple Elements

To reorder the multiple elements, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio**.
3. On the **Element Repository** page, select the required element repository for which you want to reorder the elements.
4. From **Elements List**, select the checkbox next to the required elements.
5. In the toolbar, select **Element Identifier Order**. A dialog box appears.

![](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FkPYcuPBa5R8iAADQTYM5%2Funknown.png?alt=media\&token=44ac753c-b605-4823-aabd-7f0579792a58)

6. Using the drag handle (**⠿**) on the left of each row, drag and drop the identifiers to reorder them according to the required priority sequence.
7. Select **Save**.

{% hint style="info" %}
**Note**:

* If you have reordered the element identifiers, you can view reordered elements only in the **Details** dialog.
* Reordering the **Element Identifier Order** applies the new order to all elements in the Element Repository.
  {% endhint %}

## Reordering Element Identifiers for Individual Element

To reorder an individual element, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
2. Select **Design Studio**.
3. On the **Element Repository** page, select the required element repository for which you want to reorder the elements.
4. In the **Elements List**, hover over the required element and select the **Edit** icon. The **Details** pane opens on the right.

![](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FJ7X1aVvPCtaq315EQpnD%2Funknown.png?alt=media\&token=26a664b4-ad3f-4dfc-8825-9fc0175ee9f5)

5. Using the drag handle (**⠿**) on the left of each row, drag and drop the attribute rows to reorder them according to the required priority sequence.

![](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FkEwYOVKkqtzAw6sUjYxx%2Funknown.png?alt=media\&token=c8eb54e5-68c6-42df-92d8-2f14a3f691de)

5. Select **Save** Properties.


---

# 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.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/features-in-element-repository/element-identifier-order/reorder-element-and-element-properties-in-repository.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.