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 dpendencies: 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, ensure that you select the Perform Sanity Check option, and then 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 most artifacts, and they don't have an assigned ID. However, if you scroll down in the list, you will find that the three visuals we imported earlier, in Importing Visuals and Dashboards, appear with Planned Action set to None. This is because these visual artifacts were previously imported from the same system, and they have not changed from the original import. The dataset that we imported earlier, US County Population changed (we created a derived field that did not impact these three visuals), so its status is Replace.

    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
  11. Click Visuals in the top navigation menu.
  12. By default, the imported app is not visible in the navigation menu.

    To make it visible, click Modify App Menu in the left navigation.

  13. In the Modify App Menu modal, select the visibility option for the newly imported app, and click Save.

    making imported app visible in left nav of Visuals
  14. You can now see the app Documentation Collateral in the left menu.

    imported app visible