Workspace inventory

Updated at:

DataWorks Migration Assistant provides a workspace inventory feature. This feature lets you view the development assets in your workspace and identify cross-workspace task dependencies. Development assets include tables, scheduled tasks, Data Quality, resources, manual tasks, data sources, Data Service, functions, ad hoc queries, and components.

Procedure

  1. Log on to the DataWorks console. In the left navigation pane, click More > Migration Assistant.

  2. In the left navigation pane, click Advanced Features > Detect Workspace Objects, and then click Create Detection Task.

  3. Configure the parameters for the workspace inventory task.

    • Task Name: Required. Enter the name of the inventory task.

    • Select Inventory Scope: Required. You can select Cross-workspace Dependencies and DataWorks Development Assets.

    • Notes: Optional.

    Note

    Development assets are the items in your workspace, such as tables, scheduled tasks, Data Quality, resources, manual tasks, data sources, Data Service, functions, ad hoc queries, and components.

  4. Click OK.

    After you create the task, its Status changes to Detecting. To stop the task, click Stop in the Actions column. When the task's Status is Succeeded., click View Detection Report in the Actions column to view the inventory details.

    The inventory report page contains the following information:

    • Basic Information: Displays the owner, creation time, status (Succeeded.), and notes.

    • DataWorks Key Information: The left side shows an Object Statistics table listing each object type (tables, scheduled tasks, Data Quality, resources, data sources, manual tasks, Data Service, functions, ad hoc queries, and components) with its count. You can click View Details for each item. The right side shows an Object Type/Count panel.

    • Cross-workspace Dependencies: Displays a table that shows node ID, node name, node owner, node type, upstream node ID, upstream node name, and the workspace to which the upstream node belongs.