Read a record's content

Inspect JSON, tables, text, Markdown, and file-backed records.

Open a record from its source list. The header identifies the record and shows its type, source, creation information, and available size. The body loads its content separately, so metadata can remain useful even when content retrieval fails.

Content views

Structured JSON is displayed as structured content rather than ordinary prose. Table content uses a grid and can load additional row pages. Text and Markdown records use a reading view. Supported file-backed records use the appropriate file view or download experience.

The record type takes priority when selecting a specialized view, while the content's broader kind provides a fallback. For example, CSV and TSV can receive a tabular presentation even when another record with JSON content uses a structured viewer.

A file can be too large for inline viewing or use an unsupported format. Use the offered download rather than treating the lack of an inline view as an empty file. A content-loading error also differs from a missing record: the header may still show the record's metadata.

Tables inside records

Continue loading rows while more table content is available. The first page does not establish the total row count. A read-only table in Data is also different from an editable App user table.

Trace the result

Follow the source link when you need the originating connection or workflow run. If you arrived through a source list, use back navigation to return to that same group.

Do not treat the current provider file as an exact substitute for a historical record or captured extraction source. For evidence-backed App tables, open the saved cell's evidence instead. See provenance and citations and evidence.