This field takes advantage of our powerful “Dot Walking” feature. If you’re not familiar with it, we recommend checking out this article from the Knowledge Base first.
Setting Up a Dot Walking Field
Dot walking lets you access fields from related apps by using a simple, dot-based syntax.
- Start by typing the name of a reference field followed by a dot (.) — this reveals the fields available in the related app.
- Need to go deeper? Use triple dot walking to reach fields from multiple levels of related records.
Examples:
-
Contact.Work Email
brings the Work Email from the Contacts app into the Orders app. -
Contact.Account.Name
reaches into the Accounts app through the Contact reference to pull the Account Name. - Depending on how your relationships are set up, you could also type
Account.Name
directly.
This feature gives you the flexibility to bring in data across different apps with ease.
Once you’ve configured the field, don’t forget to click Save.
Note: Dot Walking Fields for multi-select fields are not currently supported.
Referencing Dynamic Calculated Fields
When referencing a Dynamic Calculated Field, it’s important to use the Dot.Walking Field Type. This is the only field type capable of processing and displaying values from dynamic calculations.
Avoid using a Reference Field Type for this purpose. If you try to reference the dynamic field through a standard reference field, it won’t appear as an option when using dot.walking.
Changing a Field’s Type
In Servis.ai, once a field is created, its type (e.g., text, number, date, boolean) cannot be modified directly. This limitation helps ensure data consistency and prevents errors that could arise from incompatible data formats.
If you need to change the type of an existing field, you’ll need to follow these steps:
- Create a New Field: Go to the Form Fields tab on your App’s Settings and create a new field with the desired type (for example, switching from a text field to a number field).
- Deactivate the Old Field: Once the transition is complete, you can choose to delete the original field or simply hide it from views to avoid confusion.