> 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/sdocs/advanced-template-logic/build-reusable-templates/component-template-how-to-article/using-component-queries.md).

# Using Component Queries

Repeat a component once per record returned by a SOQL query.

## Using Component Queries

Component Queries allow a component template to **repeat once for each record returned by a SOQL query**.

Use them for:

* LineitemsSOQL
* Related lists

This avoids standard table layouts and gives full control over styling.

### Example 1: Repeating Opportunity Sections on an Account

**Use case:** Generate an Account document that includes a formatted section for each related Opportunity.

**Parent Template (Account)**

```html
<!--{{!
<LineItemsSOQL>
  <component>Opportunity Summary Component</component>
  <soql>
    SELECT Id 
    FROM Opportunity 
    WHERE AccountId='{{!Account.Id}}'
  </soql>
</LineItemsSOQL>
}}-->
```

This query:

* Retrieves all related Opportunities
* Inserts the component once per record

**Component Template (Opportunity)**

Template Format: **Component**

```html
<h3>{{!Opportunity.Name}}</h3>

<p>
  Stage: {{!Opportunity.StageName}}<br/>
  Amount: {{!Opportunity.Amount}}<br/>
  Close Date: {{!Opportunity.CloseDate}}
</p>
```

If the Account has three Opportunities, this component renders three times.

### Example 2: Scalable Queries Using Column Fields

**Use case:** Repeat a component for a large list of records while executing only **one SOQL query**.

**Parent Template**

```html
<!--{{!
<lineitemsSOQL>
  <class>none</class>
  <soql>
    SELECT Id, Name, StageName
    FROM Opportunity
    WHERE AccountId='{{!Account.Id}}'
  </soql>

  <component columnFields="true" mergeFieldPrefix="opp">
    Opportunity Summary Component
  </component>

  <column componentMergeField="true">Id</column>
  <column componentMergeField="true">Name</column>
  <column componentMergeField="true">StageName</column>
</lineitemsSOQL>
}}-->
```

**Component Template**

```html
<h3>{{!opp.Name}}</h3>
<p>Stage: {{!opp.StageName}}</p>
```

{% hint style="success" %}
Considerations for this method:

* Use `mergeFieldPrefix`
* Every merge field must be defined in a `<column>` tag
* Only one SOQL query runs, regardless of record count
  {% endhint %}


---

# 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/sdocs/advanced-template-logic/build-reusable-templates/component-template-how-to-article/using-component-queries.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.