--- title: "Dot-Walking" slug: "dot-walking" updated: 2024-07-03T13:58:22Z published: 2024-07-03T13:58:22Z canonical: "help.symphonysummitai.com/dot-walking" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Dot-walking Dot-walking refers to the method of utilizing dot notation to traverse the relationships between items. In Apex's data model, relationships define how objects are interconnected. Dot Walking is the process of accessing fields on related objects by linking the relationships and their associated fields using dots (.). | **Use Case** | **Solution** | | --- | --- | | Let's say we have two custom objects in the ACME's ITSM application: **Employee**: Contains information about employees, including their name and department. **Department**: Stores details about departments, such as department name and location. - These two objects are related as follows: - Each employee is associated with a department through a lookup relationship. - Each department can have multiple employees. Now, suppose we want to retrieve the location of the department that an employee belongs to using dot walking. | Here's how we would do it in Apex: // Assuming 'emp' is an instance of the Employee object // We want to retrieve the location of the department the employee belongs to **String departmentLocation = emp.Department__r.Location__c;** In this example: - emp is an instance of the Employee object. - Department__r refers to the lookup relationship between Employee and Department. - Location__c is a field on the Department object containing the location information. By using dot walking (Department__r.Location__c), we can directly access the location of the department associated with the employee without needing to perform additional queries or lookups. This makes the code concise and efficient. | ## Key Benefits of Dot-walking ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Dot%20Walking%20(2)(1).png?sv=2026-02-06&spr=https&st=2026-11-17T00%3A52%3A50Z&se=2026-11-17T01%3A52%3A50Z&sr=b&sp=r&sig=z8Z9Atappuixmoz9EioNJhDotjYL8usjvohhHl1Ne%2BE%3D)Figure: Key Benefits of Dot-walking ## How to use Dot-walking as an Application Designer | **Use Case** | **Solution** | | --- | --- | | Sam the Application Designer wants to select the fields of the parent table & the related tables based on dot-walking concept, as described in the above section. | Sam can define the conditions either on the fields of the transaction table or on the related tables using the dot-walking concept as shown in the below screenshot. | ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Dot-Walking%20Example%201.png?sv=2026-02-06&spr=https&st=2026-11-17T00%3A52%3A50Z&se=2026-11-17T01%3A52%3A50Z&sr=b&sp=r&sig=i98Od78BdHb8HMrh0NDjEKCjYLSlmc5IrrESWYhoI6I%3D)Figure: Dot-walking notation By entering **Workgroup . Primary Owner . Employee Id** in the Field section, Sam can fetch the Employee Id of the Primary Owner of that Workgroup without having to access multiple tables. ## Dot-walking Within Same Table Let us consider the below transaction table: | **SR_Master** | | --- | | **SR ID** | **Caller ID** | **Symptom** | **Status** | | 1 | 1 | Need new laptop. | Closed | | 2 | 2 | Need to install new software. | Open | | 3 | 3 | Need to upgrade software. | Open | **Scenario:** Get “**Symptom**” of the **SR** **Dot-walking:** SR_Master . Symptom **Output:** | Symptom | | --- | | Need new laptop. | | Need to install new software. | | Need to upgrade software. | ## Dot-walking from Main Table To another Table Let us consider the below transaction tables: | **SR_Master** | | | --- | --- | | **SR ID** | **Caller ID** | **Symptom** | **Status** | **Workgroup** | | 1 | 1 | Need new laptop. | Closed | 1 | | 2 | 2 | Need to install new software. | Open | 2 | | 3 | 3 | Need to upgrade software. | Open | 3 | | Workgroup_Master | | --- | | **Workgroup ID** | **Wokrgroup Name** | **Workgroup Owner** | | 1 | Workgroup 1 | 3 | | 2 | Workgroup 2 | 1 | | 3 | Workgroup 3 | 3 | | User Master | | | | --- | --- | --- | | **User ID** | **User Name** | **Email id** | **Location** | **User** **Type** | **Department** | | 1 | David | david@acme.com | Pune | VIP | 2 | | 2 | Frank | frank@acme.com | Bangalore | Normal | 3 | | 3 | Mike | mike@acme.com | Delhi | Normal | 1 | **Scenario:** Get “Workgroup Owner” of the SR **Dot-walking:** SR_Master . Workgroup . Workgroup_Owner By using the Dot-walking notation (.), we can access the Workgroup_Owner by traversing from one table to another table without having to select from multiple fields. In this scenario the Workgroup Owner details are fetched by traversing from the SR_Master Table to the Workgroup_Master Table automatically.