> 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/advanced-guides/columns-and-editing.md).

# Columns & editing

Choose how to add special columns to a grid, change how users edit cells and parent fields, or show components under each row.

These guides change what a grid column shows and how users edit it, and add components under each row.

The guides differ by **what you want to add**: a column type, an editing option or an inline component.

## Which guide do I need?

| Guide                                                                                                                          | Use it to…                                                                                   | Good to know                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| [Grid - File Upload Column](https://docs.gridmate.io/advanced-guides/columns-and-editing/grid-file-upload-column.md)           | Upload files directly from a grid column.                                                    | The formula field behind the column must return an Id, which links the uploaded file.                                          |
| [Grid - File List Column](https://docs.gridmate.io/advanced-guides/columns-and-editing/grid-file-list-column.md)               | Upload, view and delete multiple files in a grid cell.                                       | Set up with a formula field that uses `gmpkg/dataGridFileListCellLWC`.                                                         |
| [Grid - Address Column](https://docs.gridmate.io/advanced-guides/columns-and-editing/grid-address-column.md)                   | Enter addresses in a column with location autocomplete, mapped to standard or custom fields. | LWS must be activated in your organization. It needs an autocomplete handler, for example `GeoApifyAutoCompleteHandler`.       |
| [Grid - Custom Column](https://docs.gridmate.io/advanced-guides/columns-and-editing/grid-custom-column.md)                     | Render your own Lightning Web Component in grid cells, in view and edit mode.                | LWS must be activated in your organization.                                                                                    |
| [Grid - Dynamic Formula Field](https://docs.gridmate.io/advanced-guides/columns-and-editing/grid-dynamic-formula-field.md)     | Add formula columns that recalculate as users edit the grid, including Apex formulas.        | End users can create formulas once **Enable Create Formula** is checked in the App Builder. Apex formula values are read only. |
| [Grid - Edit Single Cell](https://docs.gridmate.io/advanced-guides/columns-and-editing/grid-edit-single-cell.md)               | Update one field directly in the grid without opening the whole record.                      | Turned on with **Enable Cell Editing** in the App Builder.                                                                     |
| [Grid - Edit Parent Fields](https://docs.gridmate.io/advanced-guides/columns-and-editing/grid-edit-parent-fields.md)           | Edit parent record fields directly in the grid.                                              | Turned on with the **Parent Field Editing** option.                                                                            |
| [Grid - Inline Components](https://docs.gridmate.io/advanced-guides/columns-and-editing/inline-grid-setup.md)                  | Show child grids, record layouts and other components under each grid row, with split view.  | Configured in the **Record Related Components** property of the grid.                                                          |
| [Grid - Custom Inline Component](https://docs.gridmate.io/advanced-guides/columns-and-editing/grid-custom-inline-component.md) | Display your own Aura or LWC component under each grid row.                                  | Your component needs `recordId` as an attribute. An LWC component must be exposed.                                             |

## Go further

* [Javascript Formulas](https://docs.gridmate.io/package-reference/javascript-formulas.md): data types, operators and functions for formula columns.
* [Config Snippets](https://docs.gridmate.io/package-reference/config-samples.md): copy-paste JSON configurations for inline components and more.
* [Grids](https://docs.gridmate.io/product-tour/grids.md): the grids these columns and editing options apply to.


---

# 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/advanced-guides/columns-and-editing.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.
