Importing Linked Visuals

In Arcadia Enterprise, you can import linked visuals from another system using an appropriate JSON file that captures the definitions of these visual artifacts and all their dependencies (such as datasets and custom styles).

Follow these steps to import linked visuals. We previously created them in Exporting Linked Visuals.

1. Click Data in the top navigation menu.

2. Select the connection where to import the artifacts.

   We selected Documentation, 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.

   

5. The Import Visual Artifacts window modal appears.

6. Click Choose File.

   

7. Select the backup file in your file system. Here, we are getting visuals_flow_of_events.json, the file created in Exporting Dashboards.

   

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.

     

   • 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.

     

   • 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.

   After making the appropriate selections, click Import.

   

9. After processing the import *.json file, Arcadia Enterprise opens the Import interface to show its visual artifacts. Here, it displays the visual and the dataset that we saved earlier into the visual_flow_of_events.json file, during export.

   Notice also that the Planned Action column shows that this is a new import for all artifacts. At this point, none of them have an assigned ID.

   Click Accept and 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.