> 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/parent-related-list-grid.md).

# Parent Related List Grid

Show a parent record's related list in a grid on the child record page.

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

In this tutorial, we will configure **GM - Parent RelatedList Grid**.

{% stepper %}
{% step %}

### Open the page

Select an opportunity record and edit the page in the Lightning App Builder.
{% endstep %}

{% step %}

### Add the component

From the components list, search for **GM - Parent RelatedList 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 |
| ------------------- | -------------------- | ----- |
| Object Name         | **Account**          |       |
| Record Id Field     | **AccountId**        |       |
| Related list label  | **Contacts**         |       |
| Page Size           | **15**               |       |
| Custom Icon         | **standard:contact** |       |
| Show Border         | **Checked**          |       |
| Show Column Border  | **Checked**          |       |
| Show Record Details | **Checked**          |       |

Below is a step-by-step tutorial to configure the **GM - Parent RelatedList Grid** to display a grid of **Contacts** on the **Opportunity page**, based on the **Opportunity Account**.

{% embed url="<https://youtu.be/1wNA0yn2vl4>" %}
**GM - Parent RelatedList 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>Related List Grid</strong></td><td>Show related lists in an editable grid on any record page.</td><td><a href="/product-tour/grids/related-list-grid.md">Related List Grid</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 - Parent RelatedList Grid</strong></td><td>Every property of the component.</td><td><a href="/package-reference/components-library/gm-parent-relatedlist-grid.md">GM - Parent RelatedList 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/parent-related-list-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.