> 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/tutorials/components/record-grid/build-a-fixed-record-grid-with-manual-data.md).

# Build a Fixed Record Grid with Manual Data

Show a fixed comparison, such as three service plans, in a screen flow Record Grid you fill by hand, with no Salesforce records or Get Records element.

A support rep walks a customer through the renewal options during a call. The three service plans never change between calls, and they are not stored in any object, so there is nothing to query. A Record Grid in **Manual** mode holds the plans itself: one column per plan, one row each for price, response time and included hours.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FdRYVBGIxDZWZreJrJ9VR%2Frecord-grid-build-a-fixed-record-grid-with-manual-data-result.png?alt=media" alt="Record Grid with three service plans as columns, Standard, Premium and Enterprise, and rows for plan, price per month, response time and included hours"><figcaption><p>Three fixed service plans, typed into the component, with no Salesforce record behind them.</p></figcaption></figure>

## Before you start

* A screen flow with a screen to place the grid on. No Get Records element and no collection variable are needed.
* The Record Grid settings are described in the [Record Grid](https://docs.avonnicomponents.com/flow/flow-components/record-grid.md) reference.

## Steps

{% stepper %}
{% step %}

### Add the grid in Manual mode

Add an Avonni **Record Grid** to the screen and select it. At the bottom of the **Properties** tab, check that **Data Source** is set to **Manual**. A new Record Grid starts in Manual, so there is usually nothing to change.
{% endstep %}

{% step %}

### Define the rows first

Under **Row Fields**, click **Add Row Fields** once per row. Each entry has a **Label** (the text shown at the start of the row), a **Name** (the key that ties the row to the values you enter), and a **Type**:

| Label             | Type     |
| ----------------- | -------- |
| `Plan`            | Text     |
| `Price per month` | Currency |
| `Response time`   | Text     |
| `Included hours`  | Number   |

**Name** fills in as you type the **Label**, in camel case (`Price per month` becomes `pricePerMonth`). It is required and rejects special characters, so keep the suggested value unless you have a reason to change it.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FD93bquivbyVJmpfrXQBz%2Frecord-grid-build-a-fixed-record-grid-with-manual-data-row-fields.png?alt=media" alt="Record Grid property editor in Manual mode with four Row Fields entries, one open showing Label, Name and Type, and Column Header Field set to Plan" width="320"><figcaption><p>Manual mode: each row has a Label, a Name and a Type, and the column heading is one of those rows.</p></figcaption></figure>
{% endstep %}

{% step %}

### Choose the column headings

Set **Column Header Field** to **Plan**. In Manual mode this list offers only the row fields you defined in the previous step, which is why the rows come first.
{% endstep %}

{% step %}

### Enter one record per plan

Under **Records**, add three records and fill in a value for each row field:

| Plan         | Price per month | Response time    | Included hours |
| ------------ | --------------- | ---------------- | -------------- |
| `Standard`   | `49`            | `1 business day` | `2`            |
| `Premium`    | `99`            | `4 hours`        | `10`           |
| `Enterprise` | `199`           | `1 hour`         | `40`           |

Each record becomes a column, in the order you enter them. The **Plan** row also shows in the grid, just under the headings, so each plan name appears twice.
{% endstep %}

{% step %}

### Save and test

Save the flow and click **Debug**. The screen shows three columns headed Standard, Premium and Enterprise. Down the side: Plan, Price per month as a currency amount, Response time, and Included hours. The values are the ones you typed, on every run.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Manual rows can be marked **Editable**, but the **Save** interaction does not offer **Update Record(s)**: these rows have no Salesforce record behind them. To save edits to Salesforce, use a **Variable** grid as in [Edit and save values in a Record Grid](https://docs.avonnicomponents.com/flow/tutorials/components/record-grid/edit-and-save-values-in-a-record-grid.md).
{% endhint %}

## Troubleshooting

<details>

<summary>Column Header Field offers nothing</summary>

No row fields exist yet. Add the **Row Fields** entries first, then come back to **Column Header Field**.

</details>

<details>

<summary>The columns have no heading</summary>

**Column Header Field** points at a row field whose value is empty in the records. Pick the **Plan** row again, and check that every record has a plan name.

</details>

<details>

<summary>A value shows in the wrong format</summary>

The row's **Type** decides how its values display. Set **Price per month** to Currency to get a currency amount.

</details>

## Related tutorials

* [Compare records side by side with Record Grid](https://docs.avonnicomponents.com/flow/tutorials/components/record-grid/compare-records-side-by-side-with-record-grid.md): the same layout fed by real Salesforce records.
* [Edit and save values in a Record Grid](https://docs.avonnicomponents.com/flow/tutorials/components/record-grid/edit-and-save-values-in-a-record-grid.md): let users change values in the grid.


---

# 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/tutorials/components/record-grid/build-a-fixed-record-grid-with-manual-data.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.
