Importing Apps

In Arcadia Enterprise, you can import apps from another system. All you need the is appropriate JSON file that captures the complete definition of the app, including its dependencies: its own app definition, subgroup app definitions, visuals, dashboards, datasets, and custom styles.

  1. Click Data in the top navigation menu.
  2. Select the connection where to import the artifacts.

    We selected Samples, because we are connecting to the same data source for both systems.

  3. At the top of the screen, click the (supplemental) menu.
  4. In the (supplemental) menu, click the Import Visual Artifacts option.

    starting import of visual artifacts
  5. The Import Visual Artifacts window modal appears.

  6. Click Choose File.

    Import Visual Artifacts modal, default
  7. Select the backup file in your file system. Here, we are getting app_documentation_collateral.json, the file created in Exporting Apps.

    getting the backup json file
  8. In the updated Import Visual Artifacts modal, notice the import options:

    • Import to Workspace

      The drop-down menu enables you to specify the destination workspace. By default, Arcadia Enterprise imports the visual artifacts into the user's Private workspace. However, you can choose the Public workspace, or another workspace.

      Choosing the workspace for importing visual artifacts
    • Thumbnail Action

      There are three options for thumbnail handling:

      • Import from the file
      • Generate new thumbnails
      • Skip thumbnail import

      By default, Arcadia Enterprise imports the thumbnails from the file. However, you can choose to generate new thumbnails during the import process, or skip thumbnail import.

      Choosing the thumbnail handling for importing visual artifacts
    • Disregard artifacts that exist in other workspaces (Off by default)

      Before importing an artifact, Arcadia Enterprise searches for it on the system. If it already exists, it is either updated (if changed from a previous import), or left 'as is'. If it does not exist, it is imported as a new visual artifact.

      By default, the search domain is the entire system. By selecting this option, you are limiting the search to the specified workspace.

    • Check data table compatibility (On by default)

      This is a 'sanity check' that confirms that tables suitable for the incoming dataset(s) exist on the system. This means that the database and tables have the same names on the source and target systems.

    Ensure that you select the Check data table compatibility option. After making the appropriate selections, click Import.

    completing import request
  9. After processing the import *.json file, Arcadia Enterprise opens the Import interface to show the imported visual artifacts. Notice that all items saved into the app_documentation_collateral.json file during export appear on the interface.

    Notice also that the Planned Action column shows that this is a new import for some artifacts, and they don't have an assigned ID.

    We previously imported the dashboard Flight Delay Information, and its dependencies: visuals Departure Delay by Airline & Day of the week, Originating Airport, and Originating Airport by State, the Custom Style Category colors in tables, and the dataset Flight Data; see Importing Dashboards. The dataset has changed (we edited the description parameter), so the Planned Action is to Replace. The rest of these artifacts is unchanged, so they appear with Planned Action set to None.

    Click Accept and Import.

    Accept prepared import
  10. After the import completes, a Success message appears on the Import interface.

    Notice that all the artifacts have an assigned ID. These are generated by the system, sequentially. Visuals/Dashboards and datasets have separate id queues.

    Import success