Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (17.1.0) 17.0.0 16.3.x 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

Resolve Import Conflicts

When importing assets, conflicts can occur if the source and target environments differ. The import validation process identifies these issues and provides detailed error messages in the Import Report.

For details about validation types and the report structure, see Validation results.

Common conflicts

Missing catalog items, tables, or attributes

A table or catalog item exists in the source environment but not in the target.

Error message
Catalog item not found: [Table: customer_data]

To solve this:

  1. Wait until the catalog item is imported. Alternatively, create the catalog item manually in the target environment.

  2. Re-run the import validation.

Table or catalog item name mismatch

Tables or catalog items use different names across environments and do not follow the standard naming convention (for example, table_name_{dev}, table_name_{prod}).

Error message
Alias cannot be resolved to actual id

This error can also appear for missing users or groups. See groups, or stewardship configurations.

Option 1: Configure mapping

  1. Define table mapping in Global Settings > Application Settings > Import and Export > Settings.

  2. Configure scalar remappings or custom mappings to translate names between environments. See Configure Environment Mapping.

  3. Re-run the import.

Option 2: Standardize naming

  1. Rename the table in the database to follow standard naming conventions.

  2. Re-import the source into ONE.

  3. Re-run the import.

Missing users, groups, or stewardship configurations

A user, stewardship group, or configuration referenced in the asset does not exist in the target environment.

Error message
Alias cannot be resolved to actual id

Or:

Missing required field in asset: [Rule: Customer Email Validation]

The Alias cannot be resolved to actual id error can also appear for table or catalog name mismatches. See Table or catalog item name mismatch.

Option 1: Create in target

  1. Create the missing user, group, or configuration in the target environment.

  2. Re-run the import validation.

Option 2: Remove reference and re-export

  1. Remove the reference to the user, group, or property in the source environment.

  2. Re-export and re-import the asset.

The error message displays the asset name even if the problem occurs in a nested dependency. Check the asset type and path in the metadata model to identify the exact missing reference.

Missing lookup items

Error message
Lookup item not found: [Lookup > Country Codes]

To solve this:

  1. Export and import the required lookup items separately before importing assets that reference them.

  2. Ensure lookup items are referenced by name, not by ID. For details, see Referencing lookup files.

Duplicate catalog item names

This occurs when importing assets that reference catalog items from Power BI, Tableau, or Data Stories. The import matches catalog items by name, not by path, so duplicate names cause a conflict.

Error message
Too many rows loaded from database. More than one records for unique constraint. location.catalogItems.

To solve this:

  1. Ensure catalog item names are unique, or create explicit source-to-target mappings in Global Settings > Application Settings > Import and Export > Settings.

  2. If you updated names in the source environment, re-export and re-run validation. Otherwise, re-import and re-run validation.

Resolve import violations

When you import assets using the Drafts data state, the import does not fail when it encounters invalid data. Instead, a violation is recorded on the affected draft and the import continues. After the import finishes, review each violation in the Import Report and decide how to resolve it.

To understand why violations occur, see How the import matches assets.

In the Import Report, violations appear under the Reference Import Failed and Data Node Import Failed error categories.

Most violations are resolved in one of the following ways:

  • Create the missing asset in the target environment: For example, profile a missing catalog item or include the missing asset in the next export.

  • Add an ID import mapping: An explicit source ID to target ID mapping tells the import that two assets are the same one. ID mappings are entered in the Custom mappings field of an export import mapping and are reused by all future imports.

  • Adjust matching properties: Make the properties used for matching, typically names, unique and identical in both environments.

Import mappings are configured in Global Settings > Application Settings > Import and Export > Settings. See Configure Environment Mapping.

Reference not found

The imported asset references another asset that was not found in the target environment.

Error message
The system could not find any asset <asset_type> <id> referenced from property "<property>" by reference key "<reference_key>".

Specific cases of this violation are described in Missing catalog items, tables, or attributes and Missing lookup items.

To solve this:

  1. Identify the referenced asset in the source environment. The error message contains its identifier or matching key.

  2. Check whether the same or an equivalent asset exists in the target environment.

  3. Resolve the violation in one of the following ways:

    • Create the missing asset in the target environment. For example, profile the missing catalog item, or include the asset in the next export.

    • Add an ID import mapping so the reference resolves to the existing target asset.

    • Add a scalar property import mapping so the reference is matched by a property value instead of by ID.

Multiple referenced assets found

A reference on the imported asset matched more than one asset in the target environment. The matching properties are not specific enough to identify a single asset.

Error message
The system found multiple assets matching a reference of <asset_type> <id> from property "<property>" by reference key "<reference_key>".

To solve this:

  1. Identify which target assets matched. The violation lists them.

  2. Resolve the violation in one of the following ways:

    • Make the matching properties unique in both environments. For example, if two rules share the same name, rename them in both environments so that each name identifies a single rule.

    • Add an ID import mapping for the specific source and target pair.

Parent not found

The imported asset should be created under a parent asset that does not exist in the target environment. This is the same problem as Reference not found, applied to the parent of the asset.

To solve this, use the same resolutions:

  • Create the parent in the target environment, typically by including it in the next export.

  • Add an ID import mapping.

  • Adjust the matching properties so that the parent is found.

Matched more than one asset

The imported asset itself matched more than one existing asset in the target environment. This has the same root cause as Multiple referenced assets found, but applies to the imported asset rather than to one of its references.

Error message
The system found multiple assets matching <asset_type> <id> by defined matching key <matching_key>.

To solve this:

  • Make the matching properties unique in both environments.

  • Add an ID import mapping for the specific source and target pair.

Duplicate imported assets

Two assets inside the same import archive matched each other through their matching key. This usually points to duplicated data in the source environment or to matching keys that are not specific enough.

Error message
Asset <asset_type> <id> is a duplicate of an existing one. Remove the duplicate.

To solve this, fix the data or the matching keys in the source environment, then export and import again.

Troubleshooting

Archive URL expired

Cause

The export archive URL is only valid for two hours after export.

Solution

  1. Export the assets again and download the archive immediately.

  2. Import within two hours, or configure a longer retention time using the property plugin.object-storage.ataccama.one.exportimport.archive.retention.time.

MMD model mismatch

Cause

Source and target environments have incompatible metadata models.

Solution

  1. Verify that both environments are on compatible application versions.

  2. Check metadata model versions in both environments.

  3. Upgrade the target environment if necessary.

  4. Contact Ataccama Support if the models should be compatible but the import still fails.

Environment mappings not applied

Cause

Naming conventions do not match default patterns and manual mappings are not configured.

Solution

  1. Review asset names in the source environment.

  2. Configure manual environment mappings. See Configure Environment Mapping.

  3. Re-import with updated mappings.

Rules fail validation after import

Cause

Lookup items referenced by ID do not exist in the target environment.

Solution

  1. Update rule implementations to use name-based lookup references.

  2. Export and import lookup items separately.

  3. Re-import rules after lookup items are available.

DQ evaluation fails for imported SQL catalog items or VCIs

Cause

Workspaces for SQL catalog items and virtual catalog items (VCIs) are not created automatically during import.

In this case:

  • SQL catalog items import successfully but DQ evaluation fails.

  • VCIs import successfully but produce a fatal error: java.lang.IllegalStateException: endpoint not found.

Solution

  1. Manually create the required workspaces in the target environment.

  2. Re-run the import or re-trigger DQ evaluation.

Monitoring project execution fails after promotion

Cause

Connection credentials or environment-specific configurations are missing in the target environment.

Solution

  1. Verify connection configurations in the target environment.

  2. Update connection credentials (these are not exported for security reasons).

  3. Test connections before running monitoring projects.

  4. Adjust schedules and thresholds for the target environment if needed.

See also

Was this page useful?