> 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/design-and-structure/components/fields.md).

# Fields

Fields overview

Applies to **Classic App Builder**. These controls configure how a field is displayed in a component; changing its presentation is different from changing the source schema.

Fields are single record data obtained from your resources. By default, all fields from your resource will be rendered as a text, but you can switch to a more appropriate one.

For example, you have a table of your customer's details, you can click on a record to see all available fields. All records from the same collection share the same fields. For example, each customer will have a specific `Firstname`, `Lastname`, `Email`.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MFeilMy_fVmiZK9xZlP%2F-MFesczP0oC2Y9lMdHgD%2FGIF.gif?alt=media\&token=d5f62195-381e-455a-a592-8aa6b382b18f)

### Customize your fields

Your fields are what contains your data. They belong to a collection, so in order to customize them, go to Visual Builder and choose which field you will customize.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MFeilMy_fVmiZK9xZlP%2F-MFetky9y-JLO75iqQgh%2FGIF.gif?alt=media\&token=e68069a2-80d3-41f5-ab3b-122e41ab70d4)

### Field Types

By default, all fields from your resource will be rendered as a text - this is the most basic way to display your content (depending on your field type). But if you need to change your field type, you can set it up manually. For example, use a numeric presentation for quantities. Keep phone numbers as text so that leading zeros, country prefixes, and formatting are preserved.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MFeilMy_fVmiZK9xZlP%2F-MFeum1vpCnBrO5pRzeJ%2Fimage.gif?alt=media\&token=ff47c086-4f2e-4e80-a5c7-16c6e3d7fd78)

### Field Data

You can get the value of the selected record in the component by configuring the parameter transfer. For example, you want to display the `email` of the selected user.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MG5swG72SPDyQj99-TA%2F-MG5ub77PaSFfzBTd1gE%2Fimage.gif?alt=media\&token=c4f19b08-5368-4287-9f9e-fb330a403757)

### Bind a field to a selected record

See [Binding Field to Table](/classic-app-builder/binding-and-values/binding-field-to-table.md) to display a value from the selected row, and [Field types](/user-guide/data/fields/field-types.md) for source-data considerations.

Test two different records and an empty value to confirm the displayed field follows the selection. The retained images show the earlier Classic interface.


---

# 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/design-and-structure/components/fields.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.