Go To Object: naming conventions and targeting popovers and slides

Beginner

Use Go To Object reliably by following consistent object naming conventions and learn how to open popovers and navigate slide panels from scripts.

What you'll learn

How to assign and verify object names in the Inspector
A naming convention that avoids collisions across layouts
How to open a popover programmatically with Go To Object
How to navigate to a specific slide panel index
How to confirm the step succeeded with Get(LastError)

Go To Object navigates to any named layout object -- a field, button, popover, portal, or slide panel -- by its object name. It is the only script step that can programmatically open a popover or navigate a slide control, making it essential for complex UI scripting. The reliability of every Go To Object step depends entirely on the discipline of your object naming scheme.

1/3

Assign object names with a consistent convention

Select any layout object, open the Inspector, and enter a name in the Object Name field on the Position tab. A reliable convention is: [type]_[purpose]_[context], for example "popover_addNote_contacts" or "slide_detailPanel_invoices". Names must be unique on the layout; duplicates cause Go To Object to target the first match, which may not be the one you intended.

TEXT

# Recommended naming patterns:
# Fields:    fld_<FieldName>_<TableOccurrence>
# Popovers:  pop_<Purpose>_<Layout>
# Slides:    sld_<Purpose>_<Layout>
# Portals:   prt_<RelatedTO>_<Layout>
# Buttons:   btn_<Action>_<Layout>

# Examples on the Contacts layout:
# pop_addNote_contacts
# sld_detailPanel_contacts
# fld_Email_contacts

Delete All Records safely with confirmation and privilege guards Install Menu Set: custom menus and restoring default menus