> 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.md).

# Update Records

The **Update Records** interaction automatically saves end-user modifications made within a component back to Salesforce, without extra update elements in Flow Builder.

## Overview

With the **`Update Records`** interaction, end-user modifications made within the components are automatically and instantly saved, mitigating the need for additional update elements traditionally placed after integrating such components in Flow Builder.

The feature allows admins to create the interaction for automatic updates, whether end-users are applying changes in the [Data Table](https://docs.avonnicomponents.com/flow/flow-components/data-table.md) or altering the arrangement of items in the [Kanban](https://docs.avonnicomponents.com/flow/flow-components/kanban.md) by transferring them between columns.

### Tutorials

| Name                                                                                                                                                  | Description                                                                                                                                                                             |
| ----------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**Configuring Inline Editing in the Data Table**](https://docs.avonnicomponents.com/flow/tutorials/components/data-table/making-a-field-editable.md) | In this tutorial titled "Configuring Inline Editing in the Data Table," learners will acquire the necessary skills to set up and manage the inline editing feature within a data table. |
| [**Configuring Item Drop in the Kanban**](https://docs.avonnicomponents.com/flow/flow-components/kanban.md#on-item-drop)                              | The tutorial will guide users through the configuration process, ensuring that items dropped onto the board are accurately processed and saved.                                         |

## Configuration

### **On Success**

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

### **On Error**

The interactions to execute when the record update fails. Accepted interactions are: [Show Toast](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/show-toast.md), [Flow Navigation](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/flow-navigation.md), [Refresh All Queries](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/refresh-all-queries.md) and [Fire Confetti](https://docs.avonnicomponents.com/flow/component-builder/interactions-panel/fire-confetti.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://docs.avonnicomponents.com/flow/component-builder/interactions-panel/update-records.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.
