Object Naming Strategy

Intermediate

Design a consistent FileMaker layout object naming system that enables reliable scripting, conditional formatting, and Hide Object When logic.

What you'll learn

  • How to name layout objects in Inspector
  • Naming conventions that encode object type and purpose
  • How scripts use object names for navigation and attribute control
  • How Hide Object When calculations use object names

Layout objects in FileMaker can be named -- a feature that most beginners ignore but experienced developers rely on heavily. Named objects can be targeted by scripts (Go to Object, Set Object Attribute), referenced in Hide Object When calculations, and conditionally formatted. A naming convention that encodes type, function, and context turns a layout into a scriptable system rather than a collection of anonymous widgets.

1/4
1

Naming objects in Inspector

Select any layout object -> Inspector -> Position tab -> Object Name field. Enter a descriptive name. Names are case-sensitive. Objects without names can still be targeted by tab order, but named objects are far more powerful.

TEXT
// Naming convention: [Type]_[Purpose]_[Context]
// Types: btn, fld, txt, obj, portal, tab, slide, popover, web, grp

// Examples:
btn_Save_ContactDetail      // Save button on Contact Detail layout
btn_Cancel_ContactDetail    // Cancel button on same layout
fld_Name_ContactDetail      // Name field display (read-only styled field)
portal_Invoices_Contacts    // Invoices portal on Contacts layout
tab_Details_Contact         // Tab control on Contact layout
slide_Main_Dashboard        // Slide control on Dashboard
Tab Order and Keyboard NavigationLayout Object Layer Order

Sign in to track your progress and pick up where you left off.

Sign in to FM Dojo