🚀 WHAT’S NEW

You can now see full asset names in the lineage graph! Previously, long names were trimmed with "...", but we’ve improved this for better visibility. Browsing graphs is now easier, but also, exporting a graph & sharing it for collaboration would be possible after this release.

🚀 What’s New

We’ve made it easier to see if an asset has upstream or downstream dependencies at a glance. In the Lineage tab on Atlan’s sidebar, assets with long dependency lists now show two options: "Load Upstream" and "Load Downstream". Selecting one retrieves more dependencies and updates the relevant tabs with the latest information.

Note: The number of displayed dependencies is based on a paginated request. To view all dependencies, keep clicking "Load More".

🎉 What’s new

Atlan automatically retrieves and enriches Airflow DAGs with descriptions, source owners, and tags—if included in the OpenLineage event. This ensures your metadata stays up to date with source DAGs, helping you better govern, utilize, and understand your data estate.

Learn more:

• What Atlan Crawls from Apache Airflow
• Troubleshooting Airflow Connectivity

🎉 What’s new

Product lineage just got a 10x upgrade! Product lineage will now be generated even if the data products belong to different domains or have been modified after they are created or even archived. This release includes other improvements as well, making the depiction of dependencies between your data products automated and powerful.

✨ Let’s dig deeper

First, let's briefly revisit how product lineage works. If asset A is an output port in a data product A and a regular asset (not marked as an output port) is in data product B, then product lineage will be generated between data products A and B.

Data product lineage is now updated in the following conditions:

• Data products belong to the same or different domains.
• The asset selection in a data product is modified forming new links via output ports.
• Assets are marked as output ports OR previous output ports are unmarked.
• Data products are archived, thus removing them from product lineage.
• A data products asset list is updated when new assets satisfy the filter conditions (this is for data products created using filter rules).

Product lineage is now generated in an async manner. This means there is a time gap from the last action that can update lineage (like marking an asset as an output port) to the changes being reflected in the lineage. This time gap is around 30 minutes to an hour. Most importantly, product lineage will not be generated when any participating product has more than 30,000 assets.

Any past product lineage links that were not present due to products being in different domains will now fully reflect the updated lineage, and without requiring any action from you.

👏 Give it a shot

Visit your favorite data product today and explore a more powerful product lineage experience! Create new data products to build out and experience the new product lineage. If you do not have data products enabled, you can head over to Labs (as an admin user) and turn on the products module!

Learn more: What is business lineage?

And while you try it out, let us know what you think!

🎉 What’s new

Atlan now supports efficient handling of sharded tables in BigQuery, improving crawler performance and simplifying metadata and lineage views.

✨ Let’s dig deeper

You can now manage BigQuery sharded tables with ease:

• 🚀 Faster workflows – Avoid ingesting thousands of shard tables.
• 🧠 Clearer lineage – View one table instead of many.
• 🔍 Easier filtering – Use the new “Is Sharded” filter to find consolidated tables.

👏 Give it a shot

Start exploring sharded table consolidation today and let us know your feedback!
Refer to the documentation for more details.

🎉 What's new

With this update, we’ve introduced several improvements to the workflow experience:

• Users can now add a custom name to workflows.
• We now display the user who has stopped a workflow for better traceability.
• The Run Workflow button will be disabled if a workflow is already running, preventing overlapping executions.

These changes enhance your workflow management and improve overall usability.

✨ Let's dig deeper

• Improved Workflow Management: Allowing users to add custom names to workflows provides better organization and easier identification of workflows, especially in complex processes.
• Enhanced Traceability: Displaying the user who stopped a workflow increases accountability and helps track the source of any interruptions, making it easier to troubleshoot and manage workflows.
• Prevention of Overlapping Executions: Disabling the Run Workflow button when a workflow is already running prevents accidental overlapping executions, ensuring smoother operations and preventing potential errors.

Together, these enhancements streamline workflow management, improve collaboration, and reduce the risk of operational issues.

👏 Give it a shot

Check out these enhancements and let us know what you think!

🎉 What's new

We have added a metadata popover to input and output nodes to give you additional context about them. To get the full context about the asset, you can still view it all in the sidebar.

In a previous release, we improved the navigation experience between technical and pipeline lineage. With this release, enjoy access to more information about your input and output nodes.

🎉 What's new

Announcing a few enhancements to improve your discovery of storage objects! This release helps you enrich your assets and gain better business context for decision making.

Here are the enhancements for you to check out:

• The object path of a storage object will now be available in the asset sidebar and metadata popover when viewing the lineage graph. This helps you distinguish between different objects with the same name but belonging to different storage locations.
• The container name will now be displayed in the asset preview card and sidebar to help you quickly discover and understand the relationship between your ADLS containers and objects.

🎉 What's new

You can now use the display name of your custom metadata attributes to update your dbt assets in Atlan!

Atlan now supports two ways to enrich custom metadata for your dbt assets programmatically:

• businessAttributes — supports the existing method of using hashed-string names.
• businessAttributeNames — accepts display names for custom metadata in a human-readable format.

Enjoy additional flexibility to collaborate with key stakeholders as you enrich your dbt assets in Atlan.

Learn more: Change custom metadata on assets

🎉 What's new

Announcing a revamped lineage experience for Microsoft Power BI dataflows!

Data teams rely almost exclusively on Power BI dataflows to pull data into Power BI from upstream sources such as Snowflake, Oracle, and more. Dataflow lineage is critical for helping data teams trace root cause or impact analysis efficiently through Atlan. This made us go back to the drawing board to ensure a smoother experience for our users.

✨ Let's dig deeper

With this release, you can explore the following updates:

• Power BI dataflows cataloged as native assets.
• Power BI dataflows represented as assets on the lineage graph instead of being represented as processes.
• Nested dataflows represented on the lineage graph.
• Introducing a new asset type, dataflow entities. These will be represented as column assets in Atlan.
• Support for column-level lineage from upstream sources. This includes dataflows and dataflow entities, thus providing greater visibility on the lineage graph and impact analysis report.

👏 Give it a shot

Explore the enhancements to Power BI dataflows that were built with you in mind!

Learn more: What does Atlan crawl from Microsoft Power BI?