> 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/dynamic-components.md).

# Dynamic Components

## Dynamic Components

Dynamic components allow you to determine **which component is rendered at runtime** based on Salesforce data.

### Example: Language-Based Component Selection

If you have components named:

* `Pricing Sheet English`
* `Pricing Sheet Spanish`

You can dynamically reference them:

```
{{{{!Pricing Sheet {{!Opportunity.Language__c}}}}}}
```

{% hint style="info" %}
When to use Dynamic Components:

* Small, known sets of components
* 1 variable dimension such as language, region, or tier
* Clean naming conventions

Avoid when:

* More than \~2 variables
* Component selection depends on record lists
* Scalability and maintainability are concerns
  {% 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 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://help.sdocs.com/sdocs/advanced-template-logic/build-reusable-templates/component-template-how-to-article/dynamic-components.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.