> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references.md).

# Related List References

Learn how to build, query, format, and troubleshoot direct SOQL related lists in S-Docs. Start with structure, then move through SOQL, attributes, and examples.

Use this section when you need exact syntax for direct SOQL related lists.

These reference pages help you build child-record tables, tune queries, format output, and start from working patterns.

{% hint style="info" %}
If you need a first build walkthrough, start with [How to Create Your First Related List](broken://spaces/WKNnJmhJBQwhdk5WBFsi/pages/CSG2qnpc1sicdKxyJATw).

If you already have a table and need exact syntax, stay in this reference set.
{% endhint %}

{% hint style="success" %}

#### Recommended path

If you are new to related list references, read these pages in order:

1. [Related List Structure](https://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references/related-list-structure.md)
2. [Introduction to SOQL](https://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references/introduction-to-soql.md)
3. [Related List Attributes](https://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references/related-list-attributes.md)
4. [Related List Working Examples](https://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references/related-list-working-examples.md)

Start here when you want the fastest path from syntax to working output.
{% endhint %}

Start with one of these four reference paths:

<table data-card-size="large" data-column-title-hidden data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>Related List Structure</strong></td><td>Learn the required tags and how each part of the block works.</td><td><a href="https://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references/related-list-structure.md">Related List Structure</a></td></tr><tr><td><strong>Introduction to SOQL</strong></td><td>Review `SELECT`, `WHERE`, `ORDER BY`, `LIMIT`, aggregates, and relationship queries.</td><td><a href="https://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references/introduction-to-soql.md">Introduction to SOQL</a></td></tr><tr><td><strong>Related List Attributes</strong></td><td>Format numbers and dates, handle blanks, merge values, and render conditionally.</td><td><a href="https://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references/related-list-attributes.md">Related List Attributes</a></td></tr><tr><td><strong>Related List Working Examples</strong></td><td>Start from working patterns for grouped totals, parent traversal, and conditional output.</td><td><a href="https://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references/related-list-working-examples.md">Related List Working Examples</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://help.sdocs.com/developer-hub/template-configuration-and-styling/related-list-references.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.
