Text Area

A multi-line text field for content that runs to sentences or paragraphs.

Where to find it

Architect Panel → Data:

• Datastores — the datastore, then Table Designer to add or edit a field

What it stores

Plain text with line breaks preserved, and no formatting — no bold, no lists, no links. If you need those, the WYSIWYG editor is the right type.

When to use it

• Descriptions, notes, comments, instructions.
• Anything a person writes in prose.
• Content whose length you cannot predict.

It is for prose, not data

The important discipline. A text area is where information goes to become unqueryable — you can search it, but you cannot group by it, count it or report on it meaningfully.

So if somebody will ever ask "how many of these are X", X needs to be its own field. Recording it in prose means the answer is a person reading every record.

Watch what accumulates in it

Text areas attract structure over time. A "Notes" field that consistently contains a date, a name and an outcome is three fields waiting to be created, and the sooner you notice the less history there is to migrate.

Reading a sample of what people have actually written is the quickest way to find the fields your model is missing.

Search finds it; reports do not

Text areas are searchable, so a value in one is findable. That is genuinely useful and it is not the same as reportable — searching finds records containing a word, and reporting needs the value in a field of its own.

Consider the timeline instead

Where a text area is being used as a running log — people appending updates with dates — the activity stream is the better home. It gives each entry an author, a timestamp, a type and a visibility, none of which a text area has.

A note appended to a text area loses who wrote it and when, which is exactly what somebody will want to know later.

Size the box to the content

A box three lines tall invites three lines. Where you want a paragraph, show a box that looks like it expects one — people write to fill the space they are given.

Worked example

A case datastore has a text area for background. Reviewing a sample shows most entries begin with a referral source and a date, so both become proper fields. The text area keeps the narrative, the two new fields make the referral report possible, and running updates move to the record's timeline.

Recommendations

• Anything you will count belongs in its own field.
• Read a sample of what people write — it reveals missing fields.
• Use the timeline for running updates, not a text area.
• Reach for WYSIWYG only if formatting genuinely matters.