Appearance

Relationship Display Configuration ​

Table Configuration > Relationship Display Configuration

Control how relationships between your tables appear in forms and interfaces with clear, business-friendly labels that help users understand data connections.

What is Relationship Display Configuration? ​

Relationship Display Configuration lets you:

  • Rename relationships - Change "customer_ref" to "Customer" in forms
  • Create intuitive labels - Show "Order History" instead of "orders" in sections
  • Improve user understanding - Help users navigate data connections clearly
  • Match business terminology - Use language that makes sense to your team

How Relationship Display Works ​

Relationship Types ​

Belongs-To Relationships: One record belongs to another (Order belongs to Customer)

  • Appear as selection fields in forms
  • Display name becomes the field label

Has-Many Relationships: One record has multiple related records (Customer has many Orders)

  • Appear as sections in forms
  • Display name becomes the section header

Many-to-Many Relationships: Records connect in both directions (User and Project)

  • Appear as selection or management interfaces
  • Display names clarify the connection type

Where Display Names Appear ​

  • Form section headers for has-many relationships
  • Field labels for belongs-to relationships
  • Navigation context when moving between related records
  • Interface clarity throughout your platform

Note: Relationship fields also benefit from proper field configuration. See Field Configuration to add descriptions and control positioning of relationship fields in forms.

How to Configure Relationship Display ​

Finding Relationships to Update ​

  1. Go to Settings → Table Relationships
  2. Browse the relationship list or filter by source table
  3. Look for relationships with technical names that need improvement
  4. Prioritize relationships used frequently in forms

Updating Display Names ​

  1. Click on the relationship record you want to modify
  2. Find the Display Name field
  3. Enter a clear, business-friendly name
  4. Save changes

Changes take effect immediately across all forms and interfaces.

Choosing Good Display Names ​

Use business language: Choose names like "Customer", "Order History", "Team Members" instead of "customer_ref", "user_projects", "order_items".

Examples ​

E-commerce Order Management ​

Before: Order form shows "customer_ref" field, Customer record has "orders" section After: Order form shows "Customer" field, Customer record has "Order History" section

Customer service improves through clear order history access and faster issue resolution.

Project Management System ​

Before: Project record shows "project_users" section, User profile shows "user_projects" section After: Project record shows "Team Members" section, User profile shows "My Projects" section

Team collaboration improves with intuitive project assignment and clearer role understanding.

Customer Support System ​

Before: Ticket form shows "assigned_user" field, Customer record has "support_tickets" section After: Ticket form shows "Assigned Agent" field, Customer record has "Support History" section

Support agents resolve tickets 30% faster with clearer customer context and assignment visibility.

Best Practices ​

Use Business Language: Choose names that match how users think about relationships. Avoid technical database terminology.

Provide Clear Context: Names should clearly indicate what the relationship represents and make sense where they appear.

Consider Both Directions: Think about how the relationship name works from both the source and target table perspectives.

Common Questions ​

Do relationship display names affect my data? No, only the interface labels change. Your actual data and database relationships stay the same.

Can I use the same display name for multiple relationships? Yes, but make sure each name provides clear context for its specific relationship.

What happens if I don't set a display name? The system uses the technical relationship name, which may be confusing to users.

Next Steps ​

Complete your table configuration by exploring these related areas:

Enhance your relationship management with these advanced features:

  • Custom Views - Add custom buttons and actions to your tables for enhanced relationship management
  • View Actions - Design effective action buttons for your custom views
  • Smart Input - Use AI to help create related records faster and more accurately

Back to Overview ​

Return to Table Configuration for a complete overview of all configuration options.