The quick answer
On Results, add a Formula (Text) column that references the Long Text field’s internal ID. Keep the direct field beside it while comparing the previews. In this dated example, the formula displays more of the note but still truncates it. Open the record to inspect the stored value.
Before you start
This walkthrough uses a synthetic local reconstruction of a native comparison observed on 16 October 2026. The prepared Service Note Preview Comparison search returns Copper Fitting Service Note, record 27. Its stored Long Text field contains a 1,600-character ASCII note and the expected ending marker END-OF-NOTE-1600XYZ.
The separate native test showed 241 characters plus (more...) in the direct column and a 1,000-character prefix in Formula (Text). Those counts describe that account and fixture. They establish no universal UI limit or export/API result. The recording checks the complete local field against its prepared value before and after changing the search.
The custom record type, stored field and private search are already prepared. This walkthrough adds a result column; it never edits or saves the note.
01 · Compare the result with the record
Open the saved search results. The direct Service Note column shows a shortened prefix ending in (more...).
Click View on record 27. Inspect the stored note and its ending marker, then return to the results without editing the record.
02 · Add Formula (Text)
Click Edit this Search, then open Results. On the new result row, select Formula (Text). Enter the existing field ID in braces:
{custrecord_service_note}
Set Custom Label to Formula Note Preview and click Add. Keep the original Service Note column for comparison. The label names this result column; it creates no stored field.
03 · Inspect the longer preview
Click Preview. The same record appears beside a longer Formula Note Preview. Its text reaches Section 09, then stops at retain t. The expected ending marker is still missing from the grid.
A longer result without a (more...) indicator can still be incomplete. Compare the actual ending with the stored note before relying on the result as a complete value.
04 · Save the search and check the record
Click Return To Criteria, then Save. The saved comparison retains both columns and the same one-row fixture result.
Open View on record 27 again. Its ending marker remains present, and the local full-field check confirms that all 1,600 prepared characters match. Only the search definition was saved.
Common questions
Why does the result show (more...)?
In this example, the result grid shortens the displayed Long Text value. Compare it with the record before concluding that data was lost. The recorded procedure checks the same record before and after the search change.
Does Formula (Text) return the complete Long Text value?
It does not in this dated test. The formula displays a 1,000-character prefix that ends midword. The absence of a more indicator does not prove completeness, and this observed length is not a promise for another field or account.
Is this the SuiteScript 4,000-character limit?
Oracle documents a separate 4,000-byte text-column limit for search.ResultSet. Multibyte text can contain fewer characters within that limit. It does not establish the browser grid’s preview length. Long Text storage capacity is another separate limit.
Does the formula change the stored field?
The result expression reads the field while the search runs. This walkthrough performs no note edit or record save. The local before/after check compares the full field text with the prepared fixture.
Will CSV export show the entire note?
CSV export was not tested. Verify the specific export or retrieval method, field, encoding and returned length before promising complete text. This recording establishes no CSV, SuiteScript, REST, SOAP or Workbook retrieval result.