Ataccama ONE Agentic Cloud Portal ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (17.0.0) 16.3.0 16.2.0 16.1.0 16.0.0 15.4.0 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
User Community Service Desk Downloads

Prepare for Asset Promotion

Before you begin promoting assets, make sure you have the required permissions, that your target environment is ready to receive the assets, and that you understand how each asset type behaves during promotion.

Permissions

To export and import assets, you need:

  • View data access level or higher on the assets you want to export.

  • Editing access level or higher on the relevant asset types in the target environment.

  • Access to both source and target environments.

Target environment readiness

Before importing, verify that the following exist in the target environment.

Naming conventions

How you name sources, connections, and schemas across environments affects whether environment mapping works automatically or requires manual configuration.

Review and, if needed, set up your mappings before importing. See Configure Environment Mapping.

Document your organization’s naming conventions and apply them consistently across environments to minimize mapping issues during promotion.

Assets and workspaces

  • Catalog items, sources, and workspaces must already exist.

    Workspaces for virtual catalog items (VCIs) and SQL catalog items are not created automatically during import. Without the workspace, SQL catalog items might import but fail during DQ evaluation, and VCIs might import but produce fatal errors at runtime.

  • If importing monitoring projects, export and import any referenced lookup items before importing the monitoring projects.

Users and groups

All users and groups involved in stewardship and notifications must exist with the same names and structure across all environments. If a user or group cannot be resolved during import, the promotion fails.

This ensures that:

  • Stewardship assignments are preserved correctly.

  • Notifications reach the right people.

  • No manual user mapping is required in production environments.

Compatibility

  • Source and target environments must have compatible metadata models.

  • Content packs must match the application version.

What to expect per asset type

Different asset types behave differently during promotion. Review the sections for the asset types you plan to promote.

Monitoring projects

  • All dependent assets (rules, glossary terms, SQL catalog items, virtual catalog items, post-processing plans) are automatically included in the export.

  • Catalog items, sources, and workspaces must exist in the target environment.

  • Execution schedules are preserved but might need adjustment for the target environment.

  • Connection credentials are not exported and must be configured separately.

  • Roles are exported, but not concrete users. Permissions are not exported by default but can be included if needed.

  • Result history, processing results, and export files are not included — only configurations are exported.

Rules and lookup items

A DQ rule consists of components that are handled differently during promotion:

  • Always exported: Metadata (name, description, classification, rule type), implementation (logic, expressions, components, parameters), linked glossary terms, desktop components (if applicable).

  • Automatically re-mapped: Lookups and stewardship assignments are re-mapped to corresponding items in the target environment.

  • Exported with rules: Roles and permissions (unlike monitoring projects, where permissions are not exported by default).

  • Not exported: Lookup files, which must be imported separately.

All owners and stewards must exist in the target environment, matched by username.

Referencing lookup files

By default, rules reference lookup files by ID. This means that even if a lookup file with the same name exists in the target environment, the import fails if the ID does not match.

To avoid this, switch to name-based references before exporting:

  1. In the rule implementation, use Advanced Expression or the Condition Builder.

  2. Change the lookup file reference from ID-based to name-based.

  3. Ensure lookup files with matching names exist in the target environment.

Transformation plans

  • Source and target connections must be mapped correctly.

  • Transformation steps are preserved with original configurations.

  • Target locations (files, databases) might need manual adjustment.

Catalog items

  • Parent-child relationships are preserved.

  • Profiling results are not exported (only definitions).

  • Virtual catalog items (VCIs) require all dependent catalog items to exist.

  • SQL catalog items and VCIs used in monitoring projects are automatically included when promoting the monitoring project.

Glossary terms

  • Can be exported individually or as part of dependent assets (monitoring projects, rules).

  • Export includes detection rules, linked metadata, and dependencies.

  • If terms are linked with policies, the associated policies are exported as well.

  • Use standalone glossary term export when controlled terminology must be promoted independently.

Limitations

  • Export limit: Approximately 1000 entities per export (depends on entity size).

  • Published versions only: Drafts and historical versions cannot be exported.

  • Archive URL validity: 2 hours after export. If the link expires, export the assets again.

  • File size limit: 100 MB per ZIP file. For larger archives, contact Ataccama Support.

Known limitations

  • Multiple catalog items with identical names: When importing assets that reference catalog items from Power BI, Tableau, or Data Stories, the import matches catalog items by name, not by path. If multiple catalog items share the same name but have different paths, the import fails with a structure validation error: Too many rows loaded from database. More than one records for unique constraint. location.catalogItems. To work around this, create explicit source-to-target mappings in Global Settings > Application Settings > Import and Export > Settings.

  • Hidden term instances in exports: When a term is removed from a catalog item, the system creates a hidden term instance to prevent the term from being reassigned by rules. These hidden instances are currently included in exports. This does not affect functionality but may result in unnecessary data in the exported archive.

Next steps

  • Configure Environment Mapping - Set up environment mappings if your environments do not follow standard naming conventions.

  • Promote Assets - Export assets from the source environment and import them into the target.

Was this page useful?