A resource plan contains metadata information from data sources to BI portals within a workspace. This topic describes how to use resource plans to quickly copy and distribute resources.
Scenarios
Enterprise version management.
In the same environment, distinguish between Workspace A and Workspace B. Each version is imported from Workspace A to Workspace B to implement version publishing and isolation management.
In different environments, distinguish between Environment A and Environment B. The pattern is the same as above.
NoteFor multi-environment scenarios, we recommend that you use the multi-environment migration feature, which supports resource cloning and user group permissions. For more information, contact your sales representative.
One-time resource copying.
Reuse resources that have been created across workspaces to quickly start working.
Environment upgrade migration, such as one-time migration from a public cloud environment to an on-premises deployment environment.
Principles
To support enterprise version management scenarios, resource plans record one-way import mapping relationships instead of simply copying resources. For example, when you import Dashboard a from Workspace A to Workspace B, you obtain Dashboard b. In this case, the mapping relationship a -> b is recorded through the unique ID of the dashboard. After you edit Dashboard a again and import it in replacement mode, Dashboard b is directly overwritten without the need to manually clean up Workspace B.
We do not recommend that you export and import within the same workspace because this will copy dependent datasets and data sources, which can cause confusion. We recommend that you use the Save As feature.
Circular export and import is not supported. For example, if you import from Workspace A to Workspace B and then import back from Workspace B to Workspace A, new resources will be copied to Workspace A instead of replacing the original ones.
Limits
Only the Professional Edition supports resource plans.
Only organization administrators can view and operate resource plans.
Online import is limited to resource plans within the same organization. Offline import has no restrictions on resource plans.
Importing resources from a higher version to a lower version is not supported. For example, you cannot import resources from public cloud version 5.0 to on-premises deployment version 4.0.
Resource plans do not contain all metadata information and only support exporting works in the published state. The specific content is described as follows.
Category | Included content | Excluded content |
BI portals | Styles, metadata information, menu configurations, folders, etc. | Does not include menu authorization content, old versions of BI portals, etc. |
Dashboards | Styles, metadata information, query control information (including manually entered enumeration values), global parameters, folders, etc. Supports data dashboards. | Does not include old versions of dashboards, full-screen dashboards. Cross table jumps are not supported, etc. |
Workbooks | Styles, metadata information, query control information (including manually entered enumeration values), global parameters, folders, etc. | None. |
Downloads | Styles, metadata information, query control information (including manually entered enumeration values), folders, etc. | None. |
Data entry | Styles, metadata information, folders, etc. | None. |
Datasets | Supports data tables and custom SQL datasets, including metadata information, placeholders, etc. | Does not include row-level permissions, OSS data sources, lineage relationship verification, etc. |
Data sources | The configurations of the data source. | Does not include database account password information. Does not support exploration space data sources. |
Permissions | None. | Individual permissions, user groups, and tag permissions are not supported. |
Others | Supports dashboard theme templates, lineage relationships, etc. | None. |
For specific operations on resource plans, see the following documents: