Skip to main content

Asset export (basic) for enriched assets
App

The Asset export (basic) app extracts metadata for assets that have been manually enhanced or updated by users in Atlan. These aren't just raw, system-crawled assets—they're ones where users have added business context such as descriptions, owners, tags, terms, or custom metadata.

Exports can be delivered through direct download, email, or object storage (S3, GCS, ADLS).

This reference provides complete configuration details for enriched asset exports, including scope, options, and delivery mechanisms. You can also use the same Asset export (basic) app to export other types of metadata, such as glossaries and data products. See their respective references for details.

info

The exported CSV file can also be reused in the Asset Import app to load metadata back into Atlan.

Access​

The Asset export (basic) app isn't enabled by default. To use this app, contact Atlan support and request it be added to your tenant. Once enabled, enriched asset exports can be set up and run by admins or users with workflow permissions.

Define export scope​

This section defines which enriched assets are exported and how they're filtered.

Workflow name​

Specifies the display name for the workflow in Atlan. This name is used to identify the export job in the UI and logs. Choose a name that clearly reflects the purpose or scope of the enriched asset export.

Example: If you're exporting enriched assets for a specific connection, you might set:

Enriched assets export - Snowflake production

Export scope​

Enriched only: When selected, only assets that have been enriched by users (such as with descriptions, owners, tags, terms, or custom metadata) are exported. This option is useful for backing up or migrating only the additional context provided by your team. This is the recommended option for enriched asset exports.

The remaining details in this reference assume this scope has been selected.

To understand the other scopes available, see:

Qualified name prefix (for assets)​

Restricts the export to enriched assets whose qualifiedName begins with the specified prefix.

  • Leave blank to include all enriched assets.
  • Provide a prefix to restrict the scope.

Example: A prefix of default/snowflake/1234567890 exports only enriched assets under the Snowflake connection whose qualifiedName is default/snowflake/1234567890. Without a prefix, enriched assets across all connections are exported.

Include description?​

Controls whether system-provided descriptions are included in addition to user-provided descriptions.

  • Yes: Both system-provided and user-provided descriptions are included.
  • No: Only user-provided descriptions are included.

Example: A table has a system description "Sales data table autodiscovered from Snowflake" and a user description "Contains monthly sales transactions for North America". With Yes, both descriptions are exported. With No, only the user description is exported.

Include glossaries?​

Controls whether glossaries, categories, and terms are included (as a separate file) in the export.

  • Yes: Glossaries, categories, and terms are also exported (as a separate file).
  • No: Glossaries, categories, and terms aren't exported on their own. Only the associations to assets are exported.

Example: A column is enriched with the glossary term Customer ID@@@Business Glossary. With Yes, the glossary ("Business Glossary") and all its terms are exported in a separate file. The association between this term and the asset is also exported. With No, only the association between this term and the asset is exported.

Include data products?​

Controls whether data domains, subdomains, and data products linked to enriched assets are included in the export.

  • Yes: Data domains, subdomains, and data products are also exported (as a separate file).
  • No: Data products, subdomains, and data domains aren't exported on their own. Only the associations to assets are exported.

Example: A dashboard asset is enriched and linked to the data product Payments@Finance. With Yes, the data domain ("Finance") and all its products ("Payments" and others) are exported in a separate file. The association between this product and the dashboard is also exported. With No, only the association between this data product and the dashboard is exported.

Include archived?​

Controls whether archived enriched assets are included in the export. Archived objects are retained in Atlan for lineage and history but are excluded from active search and discovery.

  • Yes: Both active and archived enriched assets are included. Useful for creating a complete historical backup of enriched asset metadata or migrating all enriched assets, including inactive ones.
  • No: Only active enriched assets are included. Appropriate for exports intended for active business use or migration where only current, in-use enriched assets are required.

Example:

A database schema contains 200 tables, of which 150 have been enriched with user descriptions, owners, and tags. Of those 150 enriched assets, 50 have been archived. With Yes, all 150 enriched tables are exported (including the 50 archived ones). With No, only the 100 active enriched tables are exported.

Select delivery method​

Defines how the exported results are delivered. By default, every export is available as a direct download from the workflow run. Additional delivery methods can be configured to suit operational or sharing needs.

Direct download​

When selected, the exported CSV file is available for download directly from the workflow run in Atlan. This option is useful for ad-hoc or one-time exports where the file is immediately needed by the user who triggered the workflow.

The file can be accessed by opening the workflow run, navigating to the Outputs section, and downloading the generated CSV file. No additional configuration is required.

Email​

When selected, the exported CSV file is delivered as an email attachment. This option is useful for distributing export results automatically to specific users or teams without requiring them to log in to the workflow interface.

Email addresses​

Specifies the list of recipients who receive the export as an email attachment. Provide multiple email addresses as a comma-separated list.

Example:

[email protected],[email protected],[email protected]

Object storage​

Use this option to export the enriched assets CSV file to a cloud object store rather than providing it only as a local download or email attachment. Recommended for large exports and recurring scheduled exports.

Use this option to send the exported CSV to Amazon S3, Google Cloud Storage (GCS), or Azure Data Lake Storage (ADLS). Object storage is recommended for large exports, automated pipelines, or recurring runs where the destination bucket is managed outside Atlan.

For detailed information on configuring storage credentials, access methods, and required fields for each provider, see Object storage configuration for apps.

Assets CSV file​

For details on the CSV file produced by the app, refer to the Asset Import reference.

See also​