Dynamic Relationship Keys with Global Fields

Beginner

Build dynamic relationships that show different related records based on context by using global fields as match keys -- including multi-key globals for complex filtering.

What you'll learn

  • How global fields work as relationship match fields
  • How to build a search/filter UI using global match fields
  • How to combine multiple global keys for compound dynamic filtering
  • The limitation of global fields and per-user context

Most relationship keys are field-to-field: ContactID matches ContactID. Dynamic relationships replace one side with a global field whose value is set by the user or a script. The relationship immediately shows records matching the new value, enabling search-as-you-type filtering, dashboard context switching, and cross-table navigation without leaving the current layout.

1/4
1

Global field as a relationship match key

Define a relationship where the left-side match field is a global field (storage: global). The relationship returns records from the right table where that table's key field matches the global's current value.

TEXT
// Global on Globals table: gSelectedProjectID (Number, global storage)
// Relationship: Globals::gSelectedProjectID = Tasks_ByProject::ProjectID

// On a dashboard layout based on Globals:
// Portal of Tasks_ByProject shows tasks for the selected project
// Changing gSelectedProjectID (via script/button) updates the portal instantly
Cross-File Lookups and Reference DataRelationship Graph Refactoring

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

Sign in to FM Dojo