Consider the following troubleshooting tips when you export or import assets in bulk.
If you export data quality rule occurrences that are associated with data quality scorecards, Data Governance and Catalog does not export the primary data elements associated with the rule occurrences.
Also, if you update the rule occurrences and re-import them back into Data Governance and Catalog, the bulk import operation does not update the rule occurrences.
To make changes to these scorecard rule occurrences, use Cloud Data Profiling.
If you export assets that contain images and then re-import the exported file, the images are not re-imported back into Data Governance and Catalog.
You cannot import images using the bulk import process. Instead, use the user interface to update or add a new image.
The bulk import job fails if I create a glossary and assign it to an asset during the same job.
Creating the glossary and assigning it to an asset during the same bulk import job may cause the bulk import to fail with an error.
To associate a glossary with any asset, first create the glossary and then associate the glossary with the asset during the next bulk import job.
If you are a user with the Super Admin privilege and you mark a parent asset for deletion through the bulk import process, then all the child assets in the hierarchy are automatically deleted. This may lead to errors.
As a workaround, delete all the child assets in a bulk import operation, and then delete the parent asset in a different operation.
For the same asset, you cannot update one parent in the hierarchy and delete another parent in the hierarchy using the same bulk import job.
For example, you cannot delete the parent subdomain Payroll and update the parent domain Finance in the same bulk import job.
To work around this, first, delete the parent asset using the DELETE operation and run the bulk import operation. You can then add another parent asset using the UPDATE operation and run the bulk import operation again.