This set of features address the following real-world scenarios:

  1. Porting visual artifacts from development/testing environments to production deployments.
  2. Creating back-ups of ArcViz artifacts.
  3. Sharing these artifacts in communities.

In an enterprise environment, it is a common practice to develop and test applications in one environment before making them widely available in a client-facing production environment.

Arcadia Instant provides an easy UI method to export visual artificats (visuals, dashboards, and apps, plus theyr dependencies) by saving them to a *.json format file. This file can then be used to import the visual artifacts to a new system, where they can be successfully deployed (provided the new environment has identical data connections).

You can also migrate

Remember that ArcViz visual artifacts do not store the actual raw data, or results of queries; instead, they contain information about the layout and settings, the associated dataset, style customizations, and the query. When saving artifact information for export, Arcadia Instant also captures all these dependencies. For example, when you export a visual that uses a custom style, the export includes that custom style, as well as the dataset. As a result, when you import the visual into a new system, it looks exactly the same as it did at the source.


Export visuals and dashboards, or export complete apps.

The export generates a *.json file and saves it into the user's download directory. It can then be shared, and imported into multiple systems.

You require the Manage visuals and dashboards privilege to export visual artifacts.

See Exporting Visuals and Dashboards and Exporting Apps .


Import visuals and dashboards, or import complete apps, using the file generated by the export functionality. This import file, *.json, must be present on the client machine.

When we import artifacts, Arcadia Instant recognizes if they have been previously imported. In such cases, we update the existing artifact instead of creating a new one. This ensures that the artifacts are correctly synchronized between development and production platforms.

The necessary import privileges depend on the operation. Here are some examples:

  • On initial import, the user must have these privileges: Create datasets, explore tables, Manage visuals and dashboards, and, if custom styles are part of the backup file, Manage styles and settings.
  • If the import is only updating an existing dataset (everything else is already on the system), the user requires only the Manage dataset privilege.
  • If import is only updating visuals and dashboards, the user requires the Manage visuals and dashboards privilege. If custom styles are part of the backup file, the user also needs the Manage styles and settings privilege.

See Importing Visuals and Dashboards and Importing Apps.

App Visibility

After importing an app into the destination ArcViz, it does not show in the left navigation. The user must check the visibility option for all imported apps.

Sanity Checks

For migration to work properly, the destination system (which imports the visual artifacts) has to have a valid connection to the data, and that data must be in a table that matches the name. When you import a visual artifacts file with the Sanity Check option enabled, the import stops when it cannot find a necessary table on the connection.

Some environments use multi-connection architecture for table access. In such cases, users must disable the Sanity Check option to successfully complete import into a single connection. After the import completes, users can re-route the data connections of datasets as necessary.