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:

Wait until the catalog item is imported. Alternatively, create the catalog item manually in the target environment.
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

Define table mapping in Global Settings > Application Settings > Import and Export > Settings.
Configure scalar remappings or custom mappings to translate names between environments. See Configure Environment Mapping.
Re-run the import.

Option 2: Standardize naming

Rename the table in the database to follow standard naming conventions.
Re-import the source into ONE.
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

Create the missing user, group, or configuration in the target environment.
Re-run the import validation.

Option 2: Remove reference and re-export

Remove the reference to the user, group, or property in the source environment.
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:

Export and import the required lookup items separately before importing assets that reference them.
Ensure lookup items are referenced by name, not by ID. For details, see Referencing lookup files.

Inconsistent metadata models

Error message

MMM configuration mismatch detected. Affected nodes: [source, connection, schema]

To solve this:

Review the list of affected nodes in the Import Report.
Update the metadata model in the target environment to match the source, or adjust environment mappings to account for the differences.

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:

Ensure catalog item names are unique, or create explicit source-to-target mappings in Global Settings > Application Settings > Import and Export > Settings.
If you updated names in the source environment, re-export and re-run validation. Otherwise, re-import and re-run validation.

Troubleshooting

Archive URL expired

Cause

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

Solution

Export the assets again and download the archive immediately.
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

Verify that both environments are on compatible application versions.
Check metadata model versions in both environments.
Upgrade the target environment if necessary.
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

Review asset names in the source environment.
Configure manual environment mappings. See Configure Environment Mapping.
Re-import with updated mappings.

Rules fail validation after import

Cause

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

Solution

Update rule implementations to use name-based lookup references.
Export and import lookup items separately.
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

Manually create the required workspaces in the target environment.
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

Verify connection configurations in the target environment.
Update connection credentials (these are not exported for security reasons).
Test connections before running monitoring projects.
Adjust schedules and thresholds for the target environment if needed.

Was this page useful?