Browse and export Data
Open Data in a project and select a Container. This view shows saved records rather than transient Toolbox variables.
Find records
Section titled “Find records”Use the available typed filters and sort controls. A number filter, a text filter and a missing-value predicate have different meanings. Choose the operator matching the field’s actual type.
Continue through bounded result pages instead of assuming that the first page contains the full dataset. Field discovery and visible-column choices help with evolving data. Local column layout changes presentation; they do not alter the Container definition.
Inspect and export
Section titled “Inspect and export”Cells show a bounded wrapped preview. Use the cell preview icon when text overflows, or the row JSON command to inspect the complete received record. Missing, false, zero, null and empty text remain different values. Use available associated-file links only when you have file-read access.
Start an export with the required format and options. Supported ordinary exports include CSV, JSON and Excel where offered. Wait for completion before using the result. A failed export should not be treated as a complete dataset.
An ordinary export reads current data progressively. If records change during export, do not describe the result as an exact snapshot of one instant. For reproducible reporting, arrange a suitable business collection window and keep the export context with the report.
Exported data can include personal or commercially sensitive information collected by your Jobs. Choose a destination and sharing permissions appropriate to that content.
Remove data
Section titled “Remove data”Use the deletion command only after establishing its scope:
- Checked rows take precedence: Delete selected names the selected count.
- With no selection, a nonempty applied filter can enable Delete filtered records.
- Without either selection or an applied filter, deletion is disabled.
Review the captured selection/filter and confirmation. Current-page selection does not select every record in the dataset. A further filtered batch needs its own confirmation; uncertain outcomes require consultation rather than an automatic replay.
Removing data is separate from stopping collection. Disable the relevant Task or stop an active Session if you also need to prevent further records. Definition edits do not remove existing records automatically.
If an external data destination is configured, that result family is stored there instead of a second internal copy. Consult the selected destination; a successful external write need not appear in this Data view.
If expected rows are absent
Section titled “If expected rows are absent”Check the Session outcome, effective Push data setting, selected destination Container and collection logs. A successful Toolbox preview alone does not create saved records. See collection for the publication workflow.