> 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/projects/dynamic-components/working-with-data/child-relationship-visualization.md).

# Child Relationship Visualization

{% hint style="warning" %}
This tutorial requires installing [**the Avonni Dynamic Components Package**](https://appexchange.salesforce.com/appxListingDetail?listingId=e855ec28-bf2c-47fa-aa38-30b43948ab4f) on your Salesforce org.
{% endhint %}

## Overview

Go beyond the standard Salesforce header! This tutorial guides you through using Avonni Dynamic Components to create a **fully customized header** for your record pages. Learn how to visually arrange components to **highlight the most critical record information** (key fields, status indicators, important metrics), add relevant action buttons, and achieve a clean, personalized look tailored precisely to your users' needs – all without code.

## Final Result

Below is an example of the custom record page header you will build in this tutorial.

## Components Used

To build the custom record page header in this tutorial, we will utilize the following Avonni Dynamic Components:

* [Media Object](/dynamic-components/components/media-object.md)
* [Columns](/dynamic-components/components/columns.md)
* [Icon](/dynamic-components/components/icon.md)
* [Text](/dynamic-components/components/text.md)
* [Button Menu](/dynamic-components/components/button-menu.md)
* [Chip Container](/dynamic-components/components/chip-container.md) (used here to display status or keyword tags)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.avonnicomponents.com/projects/dynamic-components/working-with-data/child-relationship-visualization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.