Linked Records: Connect Related Data

Data that lives in isolation is only half useful. A customer record is more valuable when you can see their orders. An order is more meaningful when linked to the customer, the products it contains, and the delivery address. A project is more actionable when it shows its tasks, its team members, and its related contract.

Connection is what turns records into understanding.

Define Any Relationship

In Swifty, you define relationships between object types as part of your data model. A relation field on one object type points to another. A "Customer" field on an Order means every order can be linked to a customer.

These aren't just visual connections — they're structured data relationships that the platform understands and enforces.

One-to-Many and Many-to-Many

Real business data has all kinds of relationships:

• A customer has many orders (one-to-many)
• A project has many tasks (one-to-many)
• A product belongs to many orders, and an order contains many products (many-to-many)

Swifty supports both, defined simply as field types in your object configuration. The platform handles the underlying data structure.

Navigate in Both Directions

Once a relationship exists, you can navigate it in both directions. From a customer, see all their orders. From an order, click through to the customer. From a task, see its parent project. From a project, browse all tasks.

Related records appear as lists within the detail page — filterable, searchable, and clickable. Moving between related records feels natural, not like jumping between disconnected systems.

Relation Fields in Forms

Relation fields in forms work like smart dropdowns. Start typing a name and matching records appear. Select one, and the relationship is established. Multi-select relation fields let you link multiple records at once.

The platform validates relation fields like any other — marking them required if the business logic demands it, preventing invalid combinations where configured.

Why It Matters

Isolated records force your team to maintain connections manually — in notes, in spreadsheets, in their heads. Structured relationships maintain those connections automatically and make them visible in context.

That visibility is where real understanding of your business comes from.