> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/update-records-order.md).

# Update Records Order

The **Update Records Order** interaction saves the new order of one or more Salesforce records back to Salesforce when a user reorders items in the component.

## Overview

The **`Update Records Order`** interaction updates the order of one or more Salesforce records. When the user reorders items in the component, the new order is saved back to Salesforce automatically.

To be usable, the component must:

* Use a [Query Data Source](/flow/component-builder/data-sources/query.md).
* Have the option to sort its items.

The records order field is the first field used in the ORDER BY clause of the query.

## Configuration

### **On Success**

The interactions to execute when the records are ordered successfully. Accepted interactions are: [Show Toast](/flow/component-builder/interactions-panel/show-toast.md), [Flow Navigation](/flow/component-builder/interactions-panel/flow-navigation.md), [Refresh All Queries](/flow/component-builder/interactions-panel/refresh-all-queries.md) and [Fire Confetti](/flow/component-builder/interactions-panel/fire-confetti.md).

### **On Error**

The interactions to execute when the records order update fails. Accepted interactions are: [Show Toast](/flow/component-builder/interactions-panel/show-toast.md), [Flow Navigation](/flow/component-builder/interactions-panel/flow-navigation.md), [Refresh All Queries](/flow/component-builder/interactions-panel/refresh-all-queries.md) and [Fire Confetti](/flow/component-builder/interactions-panel/fire-confetti.md).

## Example

Imagine a sortable List component displaying onboarding steps queried from a custom object, ordered by a numeric `Order` field. When the user drags a step to a new position, the Update Records Order interaction persists the new sequence to Salesforce. On success, a Show Toast interaction confirms that the new order was saved; on error, a Show Toast interaction with the `Error` variant explains what went wrong.


---

# 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.avonnicomponents.com/flow/component-builder/interactions-panel/update-records-order.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.