Dataphin:Incrementally export a release package

Prerequisites

• You have configured settings such as deployment credentials, the storage location for release packages, permission checks, and approval configurations for cross-tenant deployment. For more information, see Cross-tenant deployment settings.

• The source environment is in maintenance mode for cross-tenant deployment. For more information, see Maintain or upgrade Dataphin.

Limitations

Cross-tenant deployment only exports the personal accounts of data quality rule owners.

Permissions

Only users with cross-tenant deployment permissions can incrementally export release packages.

Procedure

1. Log on to Dataphin with an account that has cross-tenant deployment permissions.

2. On the top navigation bar of the Dataphin homepage, choose admin center > cross-tenant deployment.

3. In the left-side navigation pane, choose cross-tenant deployment > Export Package.

4. On the Export Package page, click New Package.

5. On the New Package page, configure the parameters.

   Set export method to incremental export. Configure the other parameters in the Basic Information and Export Information sections the same way you would for a full export. For more information, see Full export of a release package.

6. Click Save and Next.

7. In the Export Scope step, select the objects to export.

   Parameter	Description
   Last Modified Date	You can select All Dates or Specify Dates. Note An object is exported only if its Last Modified Date falls within the specified date range. Objects last modified outside this range are not exported, regardless of any other changes made to them during the selected period.
   Object Type	Select the types of objects to export. Supported object types are Global, data architecture, development, tag architecture, tag, data standard, data quality, and data security. Global: Includes statistical periods, global variables, public calendars, offline scheduling templates, data sectors, compute sources, projects, data sources, object properties, and identification features. data architecture: Includes subject domains, business objects, and business activities. development: Includes offline pipelines, fact logical tables, dimension logical tables, business qualifiers, atomic metrics, derived metrics, derivative metrics, summary logical tables, resources, functions, compute tasks (supported compute tasks vary by compute engine), Database SQL, SHELL, PYTHON, VIRTUAL, metatables, mirrored tables, offline computing templates, and trigger nodes. tag architecture: Includes entities and entity IDs. tag: Includes offline datasets, offline tags, and behavioral relationships. data standard: Includes code table directories, standard set directories, common standard attributes, standard templates, standard sets, data standards, standard mapping rules, mapping relationships, code tables, and word roots. data quality: Includes rule templates and quality rules. data security: Includes data classifications, data sensitivity levels, identification features, identification results, and keys.
   Data Sector and Project	Select the data sector and project of the objects to export. This selection also determines which security identification results are exported. This filter applies to development resources but not to other resources like data sources or data quality objects. Important Project is a required field. If you do not select a project, the system may not find any objects to export.

8. Click Export Package to start the export with the current settings.

   • Click Save Package. This creates an editable draft on the package list page.

   • Click Save and Preview. This creates a draft on the package list page and redirects you to the export preview. On the preview page, you can review the package configuration and details. To return to the editing page, click Back to Edit at the bottom of the page or click Edit next to Basic Information or Export Information.

   • The export can take several minutes to several hours, depending on the amount of data.