---
sourceDocument: Brazil ServiceNow AI Platform user interface
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-user-interface
Release :
- brazil
ft:locale :
- en-US
ft:publication_title :
- Brazil ServiceNow AI Platform user interface
ft:clusterId :
- platux
bundleId :
- platux
workflow :
- Platform
---
# Dot-walking examples
# Dot-walking examples {#ariaid-title1}
Release version: Brazil
Updated September 10, 2026
 4 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of Dot-walking examples
Dot-walking in ServiceNow allows you to access and reference fields on related tables from forms, lists, scripts, and other contexts by traversing relationships using dot notation.
This capability enhances filtering, scripting, and variable use by enabling you to reach and utilize fields beyond the immediate table.
Show full answer Show less
## Using Dot-walking in Lists
In lists, such as when creating filters, you can dot-walk to related fields by selecting reference fields and then expanding to show related fields using the "Show Related Fields" option. For example, to filter incidents by the company of the caller, you dot-walk from Incident to Caller to Company. The interface indicates the depth of dot-walking with dots and allows easy navigation back to higher-level fields or removal of related fields.
## Dot-walking in Condition Builders
Condition builders support dot-walking to build detailed queries across related tables. By enabling "Show Related Fields," you can include conditions on related records. For instance, to find incidents assigned to a user named Beth Anglin, you dot-walk from Incident \> Assigned to \> User fields \> Last name, and set the condition to Last name is Anglin.
## List Collectors
When configuring forms with list collectors, dot-walking helps select fields from related forms. Reference fields are identified by a plus symbol and can be expanded to reveal related fields. Selected fields appear using their full dot-walked syntax, such as Assigned to.Active, ensuring clarity about the source of each field.
## Dot-walking in Scripts
Scripts use dot-walking syntax to access related data within server-side and client-side contexts. Server-side scripts require prefixing with `current.` to access record fields, while client-side scripts use form APIs like `gform.getReference()` without the `current` prefix. Examples include a server-side scripted approval rule accessing the manager of the ticket opener and a client-side script highlighting VIP callers by checking the `vip` field on the caller record.
## Variables and Dot-walking
Variables in templates, notifications, or forms can use dot-walking to reference nested related fields. For example, `${assignedto}` accesses the Assigned to field, and dot-walking can extend to `${assignedto.manager}` or longer chains like `${assignedto.department.manager.mobilephone}` to pull detailed related information dynamically.
## Tree Pickers
The tree picker interface provides a hierarchical, expandable view to select related records such as Configuration Items (CIs), group members, or reference elements in hierarchical tables (tables with parent fields referencing themselves). You can configure the maximum number of nodes displayed (up to 1,000) by setting the `glide.ui.grouphierarchy.maxnodes` property and enabling `treepicker=true` in the dictionary attributes of the field.
Access fields on a related table from a form, list, or script by dot-walking. This
topic includes examples of the different ways that you can dot-walk.
## List fields {#dot-walking-examples__section_m2n_3dy_h1b}
You can dot-walk to related fields in a list, such as the field list in a filter. This example demonstrates how to filter the Incident \[incident\] table by the company of the
caller who registered the incident.
When you open the list of fields that you want to filter, you see the list of available Incident table fields. The reference fields are followed by the related fields. For example,
Caller is followed by CallerUser fields, which means that Caller is a reference field, and the related fields are user fields on the Caller record.
If the related fields are not present in the list, select Show Related Fields at the bottom of the list. When you select Show Related Fields, the menu reloads to
display related fields.
When you select a related field, the menu reloads with the fields of the related table. For example, when you select Company under Caller → User fields, the field then
becomes Caller.CompanyEach selected reference is stored at the top of the fields menu, and the number of dots preceding the field label indicate how many dots from the initial record the user has
reached.
The following example image shows that the user is at Incident.Caller.Company. You can return to higher levels in the hierarchy by selecting fields located at the top of the menu. For
instance, selecting Incident fields returns to the list of incident fields.
The related fields can be removed by selecting Remove Related Fields at the bottom of the list.
## Condition builders {#dot-walking-examples__section_aj3_d53_lfb}
You can make a detailed query on a table by dot-walking in the condition builder.
To dot-walk in a condition builder, first select Show Related Fields on the fields menu. This action allows you to add fields from related tables to your query.
For example, you could dot-walk fields in a condition builder to find all Incident records assigned to one specific user, Beth Anglin.To do so, navigate to IncidentOpen, and then open the condition builder. In the fields menu, selects Show Related Fields and then open the fields menu again to select Assigned to → User fields. Opens
the fields menu again to select Last name. Then, build the following condition: \[Last name\] \[is\] \[Anglin\]. Finally, select Run. The Incident list displays only the records assigned
to Beth Anglin.
## List collectors {#dot-walking-examples__ListCollectors}
When selecting a list of fields from a list collector (for example, when you're configuring a form), you can dot-walk to fields from other forms.
To see which fields are reference fields and can be dot-walked, look for fields with a plus symbol.
Once a reference field is highlighted, the expand icon (![Expand icon]()) appears above the add icon.
Selecting the expand icon opens the list of fields from the related list in the Available pane. The following example shows that the Assigned to fields were selected. The previous lists of fields appear at the top of the list.
Once the field is added to the Selected pane, it appears with its full dot-walked syntax. (For example, Assigned to.Active).
## Scripts {#dot-walking-examples__section_nb2_kdy_h1b}
You can dot-walk within a script by invoking the dot-walk syntax. This functionality requires a knowledge of JavaScript.
For scripts that run on the server side, such as business rules, it is necessary to add current.
The following script, for example, is a scripted approval rule that requests an approval from the manager of the user who opened the ticket.
try{
current.opened_by.manager;
}
catch(err){}
For scripts that run on the client side, such as client scripts, current is not necessary. For instance, the following Highlight VIP Caller script runs on the client side.
function onChange(control, oldValue, newValue, isLoading){
//wait until there is a valid record in the field
if(newValue){
//get the caller object so we can access fields
var caller = g_form. getReference('caller_id');
var callerLabel = document.getElementById('label.incident.caller_id');
var callerField = document.getElementById('sys_display.incident.caller_id');
//check for VIP status
if(caller.vip == 'true') {
//change the caller label to red background
//style object is CSSStyleDeclaration, style names are not standard css names
if(callerLabel)
document.getElementById('label.incident.caller_id').style.backgroundColor = 'red';
//change the caller's name field to red text
if(callerField)
document.getElementById('sys_display.incident.caller_id').style.color = 'red';
}
else { //not a VIP, remove temporary styles if(callerLabel)
document.getElementById('label.incident.caller_id').style.backgroundColor = '';
if(callerField)
document.getElementById('sys_display.incident.caller_id').style.color = '';
}
}
}
## Variables {#dot-walking-examples__section_t4q_kdy_h1b}
Often, you can add variables into templates, notifications, or other forms where a value is being called from the form.
For example, ${assigned_to} is the variable for the Assigned to field.
As shown in the example, you can dot-walk to fields on the original record of any reference field. It is possible to dot-walk to any field on the assigned_to record, for example, ${assigned_to.manager}.
When you dot-walk, you can have a longer chain if you need it, as in this example: ${assigned_to.department.manager.mobile_phone}.
Sometimes, you can select this variable from a tree picker.
## Tree pickers {#dot-walking-examples__section_zny_m2z_tfb}
The tree picker interface has an expandable, hierarchical view that you can use to look up the following items:
* Configuration Items (CIs) that are subordinate to another, higher-level CI.
* Members of a certain group. For example, you would use a tree picker to look up a user in the Service Desk group.
* Reference elements for any hierarchical table. A hierarchical table is any table that has a parent field pointing back at itself. The Group \[sys_user_group\] table, for example, would be considered a hierarchical table because certain groups are children of parent groups.
{#dot-walking-examples__ul_cbz_kjy_h1b}
Note:
You can configure the tree picker to pick up to 1,000 nodes when you configure the glide.ui.group_heirarchy.max_nodes property. To set the property, open the [Dictionary attributes](https://www.servicenow.com/docs/access?context=c_DictionaryAttributes&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) for the field, and add tree_picker=true to the Attributes field. If there are multiple attributes, use a comma to separate them without any spaces between.
*[\>]: and then