Back to Nocobase

Textarea

docs/docs/en/data-sources/data-modeling/collection-fields/basic/textarea.md

2.1.275.4 KB
Original Source

Textarea

Introduction

In NocoBase, the Textarea field stores multi-line text.

It is suitable for customer notes, processing opinions, detailed addresses, and other text that might span multiple lines. Use Input for short text and Rich text or Markdown for formatted content.

Use cases

Textarea fields are suitable for these business scenarios:

  • Customer notes and internal remarks
  • Processing opinions and descriptions
  • Detailed addresses and supplementary information
  • Long plain-text content

Create and configure

On the collection's Configure fields page, click Add field and select Textarea to create this field.

SettingDescription
Field interfaceThe field interface. Textarea uses textarea, which determines how the field is entered and displayed in pages.
Field display nameThe name displayed for the field, such as Customer notes, Processing opinion, or Detailed address. Use a name that business users can recognize.
Field nameThe field identifier used internally by APIs, relation fields, permissions, and workflows. It usually cannot be changed after creation. It supports only letters, numbers, and underscores, and must begin with a letter.
Field typeThe data-layer type. Textarea uses text by default.
Default valueThe default value. When a new record has no value, NocoBase can fill this value automatically.
Validation rulesValidation rules. Supports minimum length, maximum length, fixed length, case, regular-expression, and required validation.
DescriptionA field description. Record the field meaning, entry requirements, data source, or maintainer.

:::warning Note

Field names are referenced by page blocks, permissions, workflows, and APIs after creation. Confirm the name before creating the field to avoid later configuration changes.

:::

Field behavior

The default behavior of a Textarea field is as follows:

BehaviorDescription
Default Field interfacetextarea.
Default Field typetext.
Available Field typestext, string, json.
Page componentUses a multi-line textarea in edit mode.
FilteringSupports text filters such as contains, equals, is empty, and is not empty.
SortingSupports sorting in Table blocks where supported by the data source.
ValidationSupports minimum length, maximum length, fixed length, case, regular-expression, and required validation.

Edit configuration

After creation, click Edit beside the field to edit its configuration. Edit fields to adjust how they are displayed and used in NocoBase, such as the display name, description, default value, validation rules, or field-specific settings.

When a field comes from a synchronized main-database table, editing usually maps the database field to a NocoBase Field type and Field interface.

SettingCan be editedDescription
Field display nameYesChanges the name displayed in the interface without changing the field identifier.
Field nameNoThe field identifier normally cannot be changed in the edit form after creation.
Field interfaceConditionalMain-database fields and synchronized fields can be adjusted during field mapping. Changes affect page input, display, and validation.
Field typeConditionalMain-database fields and synchronized fields can be adjusted during field mapping. Confirm that existing values can be used by the new type first.
Default valueYesAdjusts the default value for new records.
Validation rulesYesAdjusts field validation rules.
DescriptionYesAdds the field meaning, entry requirements, data source, or maintainer.

:::warning Note

Changing a Field type or Field interface is more than changing a display name. It affects field storage, input components, validation rules, filters, and workflow-variable usage. When the field contains substantial existing data, confirm that its data format is compatible first.

:::

Delete field

Click Delete beside a Textarea field to delete it. You can also select multiple fields and delete them in the main data source.

Deleting a Textarea field created in the main database usually also deletes the actual database column and its values. For a synchronized or external-data-source field, the impact depends on the corresponding data source and field origin.

:::danger Warning

Deleting a field can affect page blocks, forms, filters, permissions, workflows, APIs, imports and exports, and existing data. Confirm that the field is no longer referenced by business configuration before deleting it.

:::

Use in pages

Textarea fields are suitable for forms, details, and long plain-text content.

ScenarioUse
Form blockEnter or edit multi-line text.
Details blockDisplay long plain-text content.
Table blockDisplay a shortened value in lists.
Workflows and permissionsUse the value in text conditions and business rules.