Appearance

Relationship Display Configuration ​

Table Configuration > Relationship Display Configuration

Data doesn't exist in a vacuum; it exists in a web of connections. But raw database relationships (like fk_user_id or orders_to_customers) are unintelligible to end users.

Relationship Display Configuration allows you to define the narrative context of your data. It lets you take a generic link and give it a specific business meaning based on where it appears.

The Competitors' Compromise ​

On many legacy platforms, renaming a "Related List" often requires creating specific "View Rules" or modifying the schema itself. It's rigid. If you link Users to Projects, the system insists on calling them "Users," even if your business calls them "Squad Members."

The Simple Advantage ​

Simple treats relationships as first-class UI citizens with Contextual Identity. You can rename the connection between two tables without touching the underlying data structure. This allows you to present the exact same data (sys_user table) as "Drivers" in one context and "Reviewers" in another.

How It Works ​

Relationships are bidirectional, but they appear differently depending on which side of the connection you are viewing.

1. The "Has-Many" Context (Related Lists) ​

When viewing a parent record (e.g., Project), the relationship to its children appears as a Section Header or Tab.

  • Raw Name: project_tasks
  • Contextual Label: "Deliverables"

2. The "Belongs-To" Context (Lookup Fields) ​

When viewing a child record (e.g., Task), the relationship to its parent appears as a Reference Field Label.

  • Raw Name: parent_project
  • Contextual Label: "Belongs To Project"

How to Configure ​

  1. Navigate to Settings > Table Relationships.
  2. Filter by the Source Table (the table that "has" the relationship).
  3. Click the relationship record you want to modify.
  4. Update the Display Name.
  5. Save. The label updates immediately across all forms and related lists.

Examples: The Power of Context ​

Scenario: The Many Faces of a User ​

Imagine you have a User table. You link it to Projects in two different ways.

Relationship A: The Owner

  • Technical Name: project_owner_id
  • Configuration: Display Name = "Project Lead"
  • UI Result: On the Project form, the field is labeled "Project Lead" (not "User").

Relationship B: The Team

  • Technical Name: project_team_members
  • Configuration: Display Name = "Squad"
  • UI Result: On the Project form, the list of related users is titled "Squad" (not "Users").

Scenario: Customer Support ​

Relationship: Customer -> Tickets

  • Before: A section on the Customer page labeled "Tickets."
  • After: Change Display Name to "Support History". The UI instantly feels more professional and helpful to the agent.

Best Practices ​

  • Speak the User's Language: Don't just describe the data type ("Documents"); describe the business purpose ("Signed Contracts").
  • Be Specific: If a Customer has multiple lists of Orders (Active vs. Archived), ensure the Relationship Display names clearly distinguish them (e.g., "Open Orders" vs. "Order History").
  • Consistent Terminology: Ensure your Relationship Display names match the terminology used in your Field Configuration to prevent cognitive dissonance.

Next Steps ​

You have now mastered the art of Table Configuration. Your application has a professional navigation structure, intuitive forms, intelligent dropdowns, and clear data relationships.

To take your user experience to the next level, start customizing the workspace itself.

  • Custom Views: Learn how to add custom buttons and logic to your tables.
  • View Actions: Design the specific actions that trigger your business logic.