Managing Relationship Graph Complexity

Expert

Techniques for keeping a large FileMaker relationship graph readable and maintainable as it grows -- visual organization, graph audits, and complexity metrics.

What you'll learn

How to measure graph complexity with quantitative metrics
Visual organization techniques beyond anchor-buoy
How to identify and eliminate "god TOs" with too many connections
When to split a file to reduce graph complexity

A FileMaker relationship graph with 200+ table occurrences becomes overwhelming without intentional organization. Left unmanaged, it evolves into a wall of crossing lines that no one can read. This lesson covers concrete techniques to measure, visualize, and reduce graph complexity while preserving all needed relationships.

1/4

Complexity metrics for the relationship graph

Quantify complexity before and after refactoring to track progress. Key metrics: total TO count, average connections per TO, maximum connections on a single TO, and number of non-anchor-buoy connections.

TEXT

// Complexity metrics (compute from Database Design Report XML or manually):
// 1. Total TO count: target < 15 TOs per table family x number of tables
// 2. Max connections per TO: "God TO" threshold = > 10 direct connections
// 3. Non-anchor-buoy connections: connections between buoys (should be 0)
// 4. Orphan TOs: TOs with 0 connections (cleanup candidates)
// 5. Cross-sector connections: relationships between different context sectors
//    (should be minimal and explicitly documented)

// Simple audit: FM relationship graph -> select all TOs -> count in selection

Versioning Records via Relationships Relationship Documentation