Creating a Long Text Area takes a minute; configuring it correctly for the use case takes thought.
- Pick the field type carefully
Setup, Object Manager, pick the object, Fields & Relationships, New. Choose Long Text Area or Rich Text Area depending on whether formatted content is needed.
- Set the length and visible lines
Pick the length (up to 131,072). Set the number of visible lines (3-25) for the rendering height.
- Decide whether to enable indexing
If users need to search the content, enable Long Text Area indexing on the object. Be aware of storage and performance trade-offs.
- Add to page layouts
Place the field on the relevant page layouts. Position it where users naturally enter content (often below the standard fields).
- Configure field-level security
Set FLS per profile. Sensitive content in Long Text Areas should not be readable by all users.
- Plan storage growth
Estimate the average and maximum content size. Build cleanup workflows for fields that grow indefinitely.
Long Text Area or Rich Text Area.
Up to 131,072 characters; pick deliberately.
3-25; controls the rendering height.
Decides whether the field is searchable.
Controls per-profile read and write access.
- Long Text Area is not searchable by default. Enable indexing if users will search the content.
- List view and report filters do not support Long Text Area by default. Filterable text should go in a regular Text field.
- Storage adds up. Multiply 131,072 bytes by row count to estimate the worst-case storage impact.
- Rich Text Area stores HTML. Display layers must escape it correctly to avoid script injection.