> 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/user-guide/data/relationships/filter-related-records-in-classic-app-builder.md).

# Filter related records in Classic App Builder

Show the orders belonging to a selected customer in a second table component. This configures a component filter; it does not create a database relationship.

## Before you start

Add a Customers table and an Orders table to a Classic App Builder page. Orders must contain a customer ID that matches the Customers identifier.

## Configure the filter

1. Select the Orders component and open **Data**.
2. Add a filter on **customer\_id**, using **equals**.
3. Select the **Formula** control for the filter value.
4. Choose the Customers component.
5. Select **Selected Row → ID**.

## Verify

Select customer 1 and confirm that only their orders appear. Select customer 2 and check that the list changes. Test the page with no customer selected and configure the component behavior for that state.

The existing walkthrough below demonstrates the same pattern with landlords and properties:

{% @arcade/embed url="<https://app.arcade.software/share/1MRXR7LbZBZGDfIzsn2t>" flowId="1MRXR7LbZBZGDfIzsn2t" %}

This display filter is not an access-control rule. Apply the appropriate resource and app permissions separately.


---

# 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/user-guide/data/relationships/filter-related-records-in-classic-app-builder.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.