This topic describes how to use the cross-workspace cloning feature.
The cross-workspace cloning feature will be discontinued on June 30, 2025. For more information, see Discontinuation of the DataWorks cross-workspace cloning feature.
Use cases
Cross-workspace cloning supports the following scenarios:
-
Clone nodes from a workspace in basic mode to another workspace in basic mode.
-
Clone nodes from a workspace in basic mode to a workspace in standard mode.
-
Cross-workspace cloning operates on a per-node basis. Folders and workflows associated with a node are also cloned to the target workspace.
-
You cannot clone a downstream node before its upstream nodes have been cloned to the target workspace.
-
By default, cross-workspace cloning adds new nodes, folders, and workflows to the target path. If a node, folder, or workflow with the same name already exists in the target path, it will be overwritten. If you clone upstream and downstream nodes together, their dependency relationships are preserved after deployment. For more information, see Deployment Center overview.
Procedure
-
Go to the DataStudio page and open the desired workflow.
-
In the upper-right corner, click Cross-workspace Cloning. This opens the cloning page, where you can filter and clone specific nodes to the target workspace.
-
Filter the nodes to clone and select a Target Workspace. Set the Clone Object Owner (the default is Default). You can further filter nodes by criteria such as Solution, Workflow, Submitter, Object Type, Change Type, Node ID, and Submission Time.
-
Click Set Compute Engine Mapping to configure the mapping between the compute engines of the source and target workspaces.
If the target workspace contains multiple compute engines, you must map them before cloning. If you do not configure this mapping, the system clones the nodes to the default compute engine in the target workspace.
Note-
If the engine type for some of your selected nodes does not exist in the target workspace, a message appears in the Compute Engine Mapping dialog box. Select the Skip Nodes Without Target Engine Instance checkbox to filter out nodes that cannot be cloned. Otherwise, the cloning process fails.
-
The Set Compute Engine Mapping button appears only when both the source workspace and the target workspace have more than one engine instance of the same type.
-
-
Click Add to List to add the selected nodes to the To-Be-Cloned Node List.
-
In the upper-right corner, open the To-Be-Cloned Node List and click Clone All.
-
In the Compute Engine Mapping dialog box, review the engine mapping pre-check results and click OK.
-
After a success message appears, go to the target workspace to view the cloned resources. The process also typically clones the entire directory structure of the workflow.