In Cloudera Data Visualization, you can import dashboards and applications that
were exported from another system. Use the migration utility to transfer these artifacts from
development or testing environments to production, or to create backups. The import process
requires a JSON file that contains the definitions of the visual artifacts and their
dependencies, such as datasets and custom styles.
Click DATA on the main navigation bar.
Select the data connection where you want to import the artifacts.
Click in the top menu bar to open the
supplemental menu.
Select Import Visual Artifacts.
The Import Visual Artifacts modal appears.
Click Choose File, then select the file you want to
import.
Click Open.
In this example, flight-dashboard.json is selected.
Specify the destination workspace in the Import to Workspace
drop-down menu.
By default, visual artifacts are imported into your Private workspace. You
can also select the Public workspace, or another workspace shared with you.
Specify how you want to handle thumbnails.
By default, thumbnails from the file are imported.
You can choose to generate new thumbnails or skip importing thumbnails.
Define the Disregard artifacts that exist in other workspaces
option.
By default, the system searches all workspaces to check if the artifact already
exists.
Selecting this option limits the search to the target workspace.
If an artifact already exists, it is updated if changes are detected; otherwise, it
remains unchanged.
New artifacts are imported if they do not already exist.
Check data table compatibility.
This confirms that corresponding tables exist in the target system.
The database and table names must match between the source and target systems.
This option is enabled by default.
Click IMPORT.
After processing the import JSON file, the Import interface displays the
list of visual artifacts.
The Planned Action column indicates whether each artifact is a new import or
an update.
Click ACCEPT AND IMPORT to confirm.
When the import completes, a success message appears. All imported visuals, dashboards,
and datasets are assigned unique system-generated IDs. Separate ID queues are maintained
for visuals/dashboards and datasets.