> 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/template-architecture/inserting-merge-fields/additional-resources/quickly-traverse-five-levels.md).

# Quickly Traverse Five Levels

Salesforce allows SOQL queries and merge fields to traverse up to five relationship levels. Understanding these levels helps leverage existing objects efficiently. Here’s a guide to navigating five levels:

* **Starting Point**: Identify the base object (e.g., Task, Opportunity, Case).
* **Relationship Levels**: Each step represents a related object or field traversed.

### Examples

#### Example 1: Opportunity to User (via Account)

Merge Field:

```
{!Opportunity.Account.Parent.Owner.Profile.Name}
```

**Levels Breakdown**:

1. Opportunity
2. Account (related to Opportunity)
3. Parent (parent Account of Account)
4. Owner (User who owns the parent Account)
5. Profile.Name (Profile name of the User)

#### Example 2: Account to Work Order Line Items

This example SOQL relationship query returns records from the parent object `Account` and its child objects `Contacts`, `Assets`, `WorkOrders`, and `WorkOrderLineItems`.

```sql
SELECT Name,
    (SELECT LastName,
        (SELECT AssetLevel,
            (SELECT Description,
                (SELECT LineItemNumber FROM WorkOrderLineItems)
            FROM WorkOrders)
        FROM Assets)
    FROM Contacts)
FROM Account
```


---

# 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/template-architecture/inserting-merge-fields/additional-resources/quickly-traverse-five-levels.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.