The Anchor-Buoy methodology for the Relationships Graph

Intermediate

Organize your Relationships Graph using the Anchor-Buoy pattern to keep it readable, predictable, and maintainable as your solution grows.

What you'll learn

What anchors and buoys are and how to name them
How to organize the graph so each layout context is visually isolated
Why Anchor-Buoy prevents context confusion and circular relationship bugs

Anchor-Buoy is a naming and layout convention for the Relationships Graph that assigns each layout a single anchor table occurrence, with all related tables hanging off it as buoys.

1/3

Name anchors and buoys consistently

An anchor is the table occurrence that a layout is based on. It uses a plain name like "Customers". Every table it relates to gets a prefixed buoy name reflecting the anchor, like "c_Orders" or "Customers_Orders".

FileMaker Script

# Anchor-Buoy naming convention (using prefix style):
# Layout: Customers
Anchor:  Customers              ← layout is based on this TO
Buoys:   c_Orders               ← Orders related from Customers
         c_LineItems             ← LineItems via c_Orders
         c_Products              ← Products via c_LineItems
         c_Contacts              ← Contacts directly related to Customers

# Layout: Orders
Anchor:  Orders                 ← separate anchor for Orders layout
Buoys:   o_Customers            ← parent customer
         o_LineItems            ← child line items
         o_Products             ← product lookup via line items

Lookup fields vs live related fields Table occurrences: what they are and how to name them