CRM Analytics: Long Text Area Field Only Shows 255 Characters — Why and How to Fix

CRM Analytics table widget truncates Long Text Area and Rich Text Area fields to 255 characters by default. Learn why this happens and how to set the Precision length in Data Manager to show more characters.

Background

Salesforce Long Text Area and Rich Text Area fields support very large amounts of text (up to 131,072 characters; default when creating a field often shows 32,768). However, when those fields are synced into CRM Analytics (formerly Tableau CRM / Einstein Analytics) and displayed in a table widget, you may see only the first 255 characters. This is a common surprise when migrating descriptive or long-note fields into Analytics datasets.

Root cause

The dataset sync configuration (Data Manager connection settings) uses a Precision or length mapping for text fields. If Precision is left blank during the SFDC_LOCAL sync setup for that field, CRM Analytics defaults the stored/visible length to 255 characters in the resulting dataset and table widget.

How to fix it (step-by-step)

  • Open CRM Analytics and go to Data Manager.
  • Click Connections and select SFDC_LOCAL (or your Salesforce connection).
  • Click the object name that contains the Long Text Area / Rich Text Area field.
  • Locate the field in the list and click the pencil (edit) icon next to it.
  • In the Precision box, enter the desired maximum length (for example, 2000 or 32768) — set this to the number of characters you want available in the Analytics dataset.
  • Save the field mapping and re-run the data sync (or run the dataset job) so the change is applied.

Notes and best practices

  • Only set Precision to what you actually need — very large lengths increase storage and may affect performance.
  • For fields that contain formatted content, consider using Rich Text Area mapping to preserve markup if Analytics supports it for your use case.
  • If you need full original-length text for export or processing, consider storing the raw field in external storage or exporting via API rather than relying on table widgets for display.

When this applies

This applies whenever you import Salesforce text fields into CRM Analytics via the SFDC_LOCAL connection (Data Manager). It’s most relevant for admins and developers preparing datasets for dashboards that include long notes, descriptions, case details, or any multi-line text fields.

Why this matters

If you expect users to read or analyze long free-text fields in Analytics dashboards, the 255-character truncation can hide critical context. Setting the Precision correctly ensures dashboards show the right amount of detail without surprises and keeps stakeholders confident in the data presented.

For Salesforce admins and developers: check your Data Manager mappings when onboarding objects into CRM Analytics and include Precision lengths in your sync documentation and change control for future updates.