Connected Field or Text Field: Which Should You Use?

Deciding between a connected field or text field is the most consequential structural choice in most builds. Text is faster to create and produces duplication that compounds over time.

What text costs when it should be a connection

The same entity ends up existing many times, slightly differently.

One client written three ways across three records
A price updated in one place and not the others
Reports that cannot group reliably
No way to see everything relating to one entity

When text is genuinely enough

A one-off description with no other record behind it
Free-form notes nobody will filter or aggregate
An external reference you do not maintain, such as a supplier's own code
Anything that exists once and is never reused

How to decide in Jestor

Ask in Jestor whether the value names something that exists elsewhere as a record.
If it does, create the table and use a connected field.
Set the label field on the related table so selection shows names, not identifiers.
Use the connected display to surface details rather than copying them.
Reserve text for genuinely one-off values nobody will filter or sum.

Why choose Jestor for relational structures?

In Jestor, tables are a relational database at the centre of the operation, so a connected field costs nothing structurally and prevents the duplication that text invites.

A card can surface data from several linked tables at once, including a parent's parent, which means connecting adds context rather than adding navigation.

Frequently Asked Questions

When is text acceptable?

For one-off values nobody will filter or aggregate. See jestor.com.

Why do connected fields show numbers?

The label is set to an ID rather than a name.

Can a card show a parent's parent?

Yes, through the connected display.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,