Appearance

Table Display Configuration ​

Table Configuration > Table Display Configuration

In a relational database, records are identified by obscure IDs (like f47ac10b-58cc...). While computers love IDs, humans need names.

Table Display Configuration allows you to define the human-readable identity of your data. By configuring just two settings, you ensure that your records are instantly recognizable across the entire platform—in search results, reference dropdowns, navigation breadcrumbs, and relation lists.

Core Concepts ​

1. Table Display Name ​

This is how the collection is presented. It replaces the technical database table name (e.g., sys_user) with a business-friendly label (e.g., "Team Members") in the navigation bar and page titles.

2. The Display Field ​

This is the single most important setting for user experience. It determines how an individual record is represented when referenced elsewhere.

When you select a "Customer" in an "Order" form, do you want to see CUST000102 or Acme Corp? The Display Field setting controls this globally.

The Simple Advantage: Define Once, Appear Everywhere

On legacy platforms, you often have to configure "Lookup Views," "Search Layouts," and "Form Headers" separately to make a record look right. On Simple, you set the Display Field once on the table, and that identity propagates instantly to every dropdown, search result, and relationship card in the system.

How to Configure ​

Setting the Display Name ​

  1. Navigate to Settings > Tables.
  2. Click on the table you wish to modify to open its record.
  3. Edit the Display Name field (e.g., change "project_task" to "Deliverable").
  4. Save. The navigation menu updates immediately.

Setting the Display Field ​

  1. Navigate to Settings > Tables.
  2. Open the table record.
  3. Locate the Display Field dropdown.
  4. Select the field that best identifies the record (e.g., email, product_name, title).
  5. Save.

Intelligent Fallbacks ​

If you do not explicitly set a Display Field, the platform attempts to auto-detect the best identity using this priority order:

  1. A field explicitly named title.
  2. A field explicitly named display_name.
  3. A field explicitly named name.
  4. The record's id.

Advanced Pattern: Computed Identities ​

Sometimes, a single field isn't enough. You might want a Contact to appear as "Last Name, First Name (Company)".

You can achieve this without any UI code by combining Record Behaviors with Display Fields:

  1. Create a Text Field: Add a field to your table named full_display_name.

  2. Write a Behavior: Create a Record Behavior that runs on load and update to automatically populate this field.

    javascript
    export default async ({ $form }) => {
  const first = $form('first_name').value() || ''
  const last = $form('last_name').value() || ''
  const company = $form('company_name').value() || ''

  $form('full_display_name').set(`${last}, ${first} (${company})`)
}

  3. Set as Display Field: Go to the Table settings and select full_display_name as the Display Field.

Result: Your rich, computed identity now appears everywhere in the system automatically.

Examples ​

Team Members Table ​

  • Raw Data: sys_user table, ID: 99a8...
  • Configuration: Display Name = "Employees", Display Field = email
  • User Experience: Navigation shows "Employees"; Dropdowns show "alice@example.com".

Product Catalog ​

  • Raw Data: inventory_item table, ID: 11b2...
  • Configuration: Display Name = "Products", Display Field = sku
  • User Experience: Dropdowns show "SKU-999". (This might be hard to read! Better to use a computed field combining SKU and Name).

Next Steps ​

Now that your tables look professional, let's optimize the fields within them.