Skip to content

Import and export

Import and export move case tables, and their data, between workspaces. Both run as job plans and are recorded in Jobs.

Export tables

  1. Open Tables and select one or more tables.
  2. Choose Export.
  3. Choose the format and the scope:
Scope Contains
Schema only The structure, without rows
Data only The rows, without the structure
Schema + data Both, in one file
  1. Confirm. The export creates a plan; download the file when the plan completes.

What can be exported

Only tables that can be re-imported are exported:

Status Exportable Why
Active Yes It is the published version
Draft, Pending, Active pending, In plan, Syncing No The file would not match any published state
Error No The last migration did not complete

The exported schema is the active version. If a table has no active version, the latest draft is used instead — but the file is always internally consistent: the schema and the data come from the same version, so a round trip does not mix them.

Formats: JSON for a single file that can be re-imported, CSV which arrives as a ZIP with one file per table, and Excel for reading the rows.

A table of classification Configuration cannot be exported as schema only: its seeds are the data, so the dialog asks you to include them or to change the table type.

Import tables

  1. Open Tables and choose Import.
  2. Drop a .json file, or select it. Other extensions are rejected before anything is created.
  3. Review the preview: tables in the file, total rows, and the severity of the import.
  4. Choose the target domain. Importing into a domain with a different prefix is reported as a cross-domain import.
  5. Confirm, then follow the plan in Jobs.

Validation before anything is created

  • Only .json files are accepted.
  • Every table definition needs a name, a classification, and at least one column.
  • Imported tables are always created as Draft: nothing becomes active until you review and publish them.
  • A physical table name that already exists is not created twice; the summary reports it as failed.

The result is a summary with the totals of created and failed tables and the reason for each failure.

Conflicts with an existing table

When the import targets a table that already exists, you choose how to resolve it from Jobs:

Option Effect
Overwrite Replaces the table's rows with the ones in the file
Add Keeps the existing rows and appends the new ones
Merge Updates rows that match and adds the rest

Configuration tables block the import when their structure or data conflicts: the plan fails with the reason instead of silently altering the seeds.

Rows versus tables

Importing tables replaces or extends whole definitions. To load rows into a table that already exists, use CSV import on the data grid.

Permissions

Permission Allows
LURANA_CASE_TABLES_EXPORT Export tables and data
LURANA_CASE_TABLES_IMPORT Import tables and data

The full list is in Permission reference.

  • Tables — selecting the tables to move.
  • Jobs — the plans, approvals, and conflict resolution.
  • CSV import — loading rows from a file.
  • Table data — row-level export.