Records Import & Export

Sovrium moves bulk data in and out of tables three ways. Clipboard copy/paste between a data-table and a spreadsheet ships today, built on the existing batch and list endpoints. CSV import (upload a file to bulk-create records) and export (download the current view as CSV or JSON) are designed but not yet available. No configuration is required for any of them.

CSV import

Upload a CSV file to bulk-load records, with column-to-field mapping, configurable duplicate handling, and per-row error reporting on partial failures.

POST /api/tables/:tableId/import
Content-Type: multipart/form-data

Body:
  file              (CSV file)
  mapping           (JSON: { "csvColumn": "tableField" })
  duplicateStrategy ("skip" | "overwrite" | "create")
  uniqueField       (field used to detect duplicates)

The response summarizes the outcome and reports per-row errors without failing the whole import:

{
  "imported": 120,
  "skipped": 4,
  "updated": 11,
  "failed": 2,
  "errors": [
    { "row": 17, "field": "email", "error": "Invalid email format" },
    { "row": 92, "field": "amount", "error": "Expected a number" }
  ]
}

Imported records pass the same field-type validation and field-level permissions as a normal create.

Export

Export the current view of a table — all visible rows, a hand-picked selection, or the same data as JSON for developer tooling.

GET /api/tables/:tableId/export?format=csv&viewId=2&filters=JSON&fields=id,name,status
GET /api/tables/:tableId/export?format=json&fields=id,name,status
GET /api/tables/:tableId/export?format=csv&recordIds=1,2,3&fields=id,name,status

The response streams the file with an attachment disposition:

Content-Type: text/csv            (or application/json)
Content-Disposition: attachment; filename="orders.csv"

Export honors field-level read permissions — columns the caller cannot read are omitted from the file.

Clipboard

The data-table component supports spreadsheet-style copy and paste, built on the standard Records endpoints.

Paste maps tab-separated columns onto table fields (with a preview/mapping step so the user can confirm before write), then commits via a single batch create — keeping the operation atomic. Copy serializes the selected rows' visible columns to TSV.

Related pages

• Batch Operations — the atomic bulk-write path clipboard paste uses
• Filtering, Sorting & Pagination — the filter/field grammar export reuses
• Table Views — export a saved view by viewId
• Table Validation — import rows pass field-type validation
• Table Permissions — field-level read/write gates import and export