Skip to content

Columns

Definition

A column defines an attribute of the rows in a table.

Columns determine:

  • what information is stored for each row
  • the data type of that information
  • how the field is presented in forms and lists
  • how the field can be referenced in rules, classifications, and integrations

Each column belongs to exactly one table.

Configuration fields

Name

Human-readable label used throughout the interface.

The name is used in forms, lists, and filters.

API name

Identifier used when interacting with the API.

Constraints:

  • Must be unique within the table
  • Allowed characters: a–z, 0–9, _
  • Must be lowercase
  • Cannot start with a number

Description

Optional text describing the column.

This text may appear as help text in forms.

Table

Defines which table the column belongs to.

A column can only belong to a single table.

Type

Defines the data type stored in the column.

The type determines:

  • how values are stored
  • how values are rendered in forms
  • how values are interpreted by rules and classifications

The column type cannot be changed after the column is created.

Column types

The system supports the following column types.

Type Description
Short Text Single-line text input
Long Text Multi-line text input
Whole Number Integer value
Decimal Number Decimal value
Yes / No Boolean value
Date Calendar date without time
Time Time of day without date
Date & Time Date with time
Date Range Start and end date
Date & Time Range Start and end date with time
Color Color selection field
Schedule Reference to a predefined schedule

Schedule column

A Schedule column stores a reference to a schedule.

The stored value represents the identifier of a schedule that defines a repeating time pattern.

Schedules are typically used for cases such as:

  • work shifts
  • availability patterns
  • recurring assignments

Summary columns

Columns can be designated as summary columns.

Summary columns determine how rows are displayed in places where a human-readable label is required.

Examples include:

  • lists
  • search results
  • relation references

Multiple columns can be used together to create the display label for a row.

For example:

First name + Last name → "Anna Andersson"

The order of summary columns is determined by the table sort configuration, not by the column definition itself.

Validation and constraints

Columns do not define validation rules or required fields.

Validation and data requirements are implemented through:

  • classifications
  • rules

These mechanisms can enforce conditions such as required fields or value restrictions.

Ordering

The visual order of columns is defined at the table level.

See the Tables reference for details about column ordering and sorting behavior.

Modification

The following properties can be changed after creation:

  • name
  • API name
  • description

The column type cannot be modified once the column has been created.

Columns interact with several other system components.

Component Relationship
Tables Columns belong to tables
Relations Relations may reference column values
Classifications Classifications evaluate column values
Permissions Permissions may restrict visibility of column data
Interface Forms and lists are generated from column definitions
Integrations Column values are exposed through APIs and imports

Understand the concept