Data Import¶

Data Import loads a previously exported file—JSON, or ZIP if the workspace filesystem was included—into the current workspace. Create that file with Data Export.

After you upload the file, the page shows one step per group of elements actually present in it (for example, a Reports step and/or a Jobs step) — you won't see a step for content the file doesn't contain. If the file contains content for a feature that isn't enabled on this installation—for example a Jobs section on a host where that feature is off—that content is listed with a notice that it will be skipped.

Importable Elements¶

The Reports step covers:

• Languages
• Dictionaries
• Page Types
• Parameter Groups
• Global Parameters
• Global Data Sources
• Reusable Parameter Definitions
• Reusable Data Source Definitions
• File Management
• Report Types
• Themes
• Templates
• Custom Components
• Subreports
• Reports
• Default Reports

If the file contains a Jobs step, it covers:

• Workflow Definitions

You can also import filesystem content from the File Management page directly.

Handling Dependencies¶

Critical external dependencies (never in the export) must already exist in the target workspace if imported items reference them; otherwise the import fails:

• External Databases
• Google Cloud Service Accounts
• API Connections

They are used by Reusable Parameter Definitions and Reusable Data Source Definitions, and by workflows' data source bindings.

Missing references:

• If any element references another element by name (for example a template referencing a theme, a report referencing a template or subreport, a dictionary referencing a language, or a report type referencing page types) and that referenced element is not in the target workspace and is not included in the same import, the import fails.
• A workflow definition's data source bindings follow the same rule: if a binding points at a shared (global) data source by name and that data source is not in the target workspace and not included in the same import, the import fails. Data sources owned by the workflow itself are always included with it, so they never hit this case.
• Missing file references (for example an image not present in the export) still allow the import to finish, but paths show up broken.

Not Included in the Import¶

Using Data Import¶

1. Open the Admin application and go to Import / Export → Data Import.
2. Drag and drop the exported file onto the upload area, or click Browse files from your computer to choose it.
3. Review the items on each step and select or deselect what you want to import; use Previous/Next to move between steps.
4. On the last step, click Upload.

When an imported element already exists in the target workspace, choose how to resolve the conflict: Stop aborts the import, Keep existing leaves the current workspace version, and Replace overwrites it with the imported version. For workflow definitions, "already exists" is decided by matching name and version—two workflows with the same name but a different version both import side by side; replacing a workflow definition also replaces all of its data source bindings.

Font Installation¶

The left sidebar includes a toggle to automatically install all fonts detected in the import archive. This is useful when the archive contains fonts needed for document conversion (such as PPTX).

Bootstrapping a Workspace at Startup¶

ImportFilePath accepts the JSON export file. FileSystemImportPath accepts the filesystem content (directory or files). If the export produced a ZIP, extract it first—point ImportFilePath at the JSON inside and FileSystemImportPath at the filesystem content. See Workspace Initialization for details.