> For the complete documentation index, see [llms.txt](https://docs.gridmate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridmate.io/product-tour/records.md).

# Records

Choose how to show a record's details, KPIs, stages or app links on a Lightning page.

These components show a single record, or one of its fields, on a Lightning page: a layout of its fields, KPI rings, a path of stages, or a switcher between Lightning apps.

They differ in **what they show**, so start with the table below.

## Which record component should I use?

| Component                                                                                      | Use it when you want…                                                                                                                    | Good to know                                                                                                                                                        |
| ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Record Layout](https://docs.gridmate.io/product-tour/records/record-layout.md)                | To display record details or a related parent record, such as the sponsor on an Opportunity page, with a JSON layout and record actions. | Added with **GM - Record Layout** in the Lightning App Builder. To show information based on the related record, put those fields in a separate GM - Record Layout. |
| [Record Layout (LWC)](https://docs.gridmate.io/product-tour/records/record-layout-lwc.md)      | Multi-column layouts with dynamic forms, conditional coloring, error handling and edit modes, on any standard or custom object.          | Edit/Form mode requires wrapping the component in an Aura wrapper.                                                                                                  |
| [Record KPI](https://docs.gridmate.io/product-tour/records/record-kpi.md)                      | Currency or percentage fields shown as KPI rings.                                                                                        | Used inside the GM - Record Layout component. Two KPI types are supported: Currency and Percentage.                                                                 |
| [Field Path](https://docs.gridmate.io/product-tour/records/field-path.md)                      | A path for any field, with stages that group several values, for example a path for the case status.                                     | Not tied to one specific path: **GM - Field Path** can be used for many fields on the same object.                                                                  |
| [Record App Switcher](https://docs.gridmate.io/product-tour/records/app-switcher-in-action.md) | To switch between Lightning apps in two clicks.                                                                                          | Embedded as a utility bar item. If the list of apps is empty, the end user should reorder the apps from the App Launcher.                                           |

## Go further

* [GM - Record Layout](https://docs.gridmate.io/package-reference/components-library/records/gm-record-layout.md): every property of the component.
* [Enhanced Record Layout](https://docs.gridmate.io/advanced-guides/other-components/enhanced-record-layout.md): layout actions, live validation rules, Apex validation and reusable metadata configs.
* [Utility Bar](https://docs.gridmate.io/product-tour/smart-grids-in-utility-bar.md): add GridMate components to a Lightning app utility bar or an Experience Cloud site.


---

# 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.gridmate.io/product-tour/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.
