> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/binding-and-values/binding-form-to-table.md).

# Connect a table to an edit form

Applies to **Classic App Builder**. Screens and recordings in this section show the Classic interface.

Show the selected table record in a form, then update that specific record.

**Before you start:** prepare a table and form for the intended resource, a stable record identifier, and two distinguishable synthetic records.

## Configure the data flow

1. Connect the table to the intended collection.
2. Select a test row.
3. In the form or its field settings, use the available **Bind** or **Functions** control to reference values from the table's selected record.
4. Match each source field to the corresponding form input.
5. Configure the submission operation to update the selected record, using its stable identifier and the form's editable values.
6. Configure any required post-submit refresh through the relevant component action.

![Classic binding example showing a selected table value referenced by an input](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FAUXI2L45qqMIcRQoOMPU%2Fimage.png?alt=media\&token=fbe0ee6b-001f-4de5-8d60-68f98e663b7d)

The screenshot illustrates the binding principle; the form and operation controls depend on the component you use. See [Binding components](/classic-app-builder/binding-and-values/binding-components.md) and [Actions](/classic-app-builder/actions-and-logic/actions.md) for the controls.

## Verify the result

Select record A, then record B: the form should follow the selection. Change one field on B, submit, and verify that only B changed in the source. Test an empty selection and a user who cannot update the record.

If the wrong record changes, inspect the identifier passed to the update operation before changing the display binding.

## Existing Classic video

{% embed url="<https://www.youtube.com/watch?v=rdM-p_fgi-k>" %}


---

# 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.jetadmin.io/classic-app-builder/binding-and-values/binding-form-to-table.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.