> 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/grids/list-view-grid.md).

# List View Grid

Display any Salesforce list view in a grid with search, inline edit and no column limits.

GridMate provides a lightning grid component **GM - ListView Grid** to display list views with advanced features and bypass Salesforce standard UI limitations like the number of columns and rows.

In this tutorial, we will create an app page for account management using **GM - ListView Grid**.

{% stepper %}
{% step %}

### Create an app page

From Setup, create an app page in the Lightning App Builder.
{% endstep %}

{% step %}

### Add the component

From the components list, drag and drop the component **GM - ListView Grid**. The grid component is now ready for configuration in the Lightning App Builder.
{% endstep %}

{% step %}

### Configure the properties

The property values can be configured to tailor the data grid to the needs of the end-user. To perform a quick configuration, populate the property values in the table below.
{% endstep %}
{% endstepper %}

## Properties

| Property            | Demo value             | Notes |
| ------------------- | ---------------------- | ----- |
| Related Object Name | ***Account***          |       |
| ListView Name       | ***AllAccounts***      |       |
| Row Limit           | **500**                |       |
| Page Size           | **50**                 |       |
| Custom Icon         | ***standard:account*** |       |
| Grid Height         | **9999**               |       |
| Search Fields       | **Name,BillingCity**   |       |
| Wildcard Search     | **Checked**            |       |
| Show Border         | ***Checked***          |       |
| Show Column Border  | ***Checked***          |       |

Below is a step by step tutorial to configure the **GM - ListView Grid** component.

{% embed url="<https://youtu.be/MhtpVKLX7Fo>" %}
GM - ListView Grid
{% endembed %}

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Grid - Mass/Record Actions</strong></td><td>Add toolbar, global and record actions to the grid.</td><td><a href="/advanced-guides/grid-actions/actions-library.md">Grid - Mass/Record Actions</a></td></tr><tr><td><strong>Grid - Advanced Configuration</strong></td><td>Generate grid property values step by step with the Config Wiz.</td><td><a href="/advanced-guides/grid-setup/grid-configuration.md">Grid - Advanced Configuration</a></td></tr><tr><td><strong>GM - ListView Grid</strong></td><td>Every property of the component.</td><td><a href="/package-reference/components-library/gm-listview-grid.md">GM - ListView Grid</a></td></tr></tbody></table>


---

# 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/grids/list-view-grid.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.