🎉 What's new

The wait is over, Atlan now supports column-level lineage for your dbt models! Although column-level lineage for dbt models is currently unavailable at source, Atlan presents a new custom SQL-parsing algorithm to generate column-level lineage for your dbt models.

Explore, analyze, and better understand your dbt assets with column-level lineage in Atlan! And as you do, let us know what you think. Note that due to the limitations of SQL parsing, Atlan cannot guarantee generating lineage for all columns.

If you have an existing dbt integration in Atlan, you will need to rerun the crawler to generate column-level lineage. For any new integrations, column-level lineage will be available from the start.

🎉 What's new

Atlan now enables you to customize the landing page for your personas! This can help you curate a personalized and focused experience for your users.

✨ Let's dig deeper

You can now set landing page preferences for a persona! This will enable users that belong to that persona to directly navigate to the page you've selected once they log into Atlan. This landing page can be asset discovery, glossaries, Insights, or data products (if enabled), ensuring a more focused experience.

👏 Give it a shot

Enjoy the power of transporting your users to their relevant module in Atlan with customized landing pages. And as you try it, let us know what you think!

Learn more: How to create a persona

🎉 What's new

Atlan now supports cross-project lineage for Looker! This release helps enhance data discovery and tracking lineage across your Looker projects.

Atlan now supports:

• Lineage across your Looker projects
• Field-level lineage for looks, tiles, and dashboards
• Tracking explore fields in a Looker dashboard, including upstream lineage to original SQL columns

If you have an existing Looker integration in Atlan, you will need to rerun the crawler to generate cross-project lineage. For any new integrations, cross-project lineage will be available from the start.

🎉 What's new

Introducing a new toggle in the admin center that allows Atlan admins to:

• Limit the view of all glossaries via glossary policies in personas 
• Unlock the ability to switch personas while viewing glossaries for their users

✨ Let's dig deeper

As an Atlan admin, you can turn on the Persona switcher for Glossary toggle from Labs in the admin center. This will allow your users to switch between personas while viewing glossaries. 

Once you have restricted glossary visibility:

• If a glossary policy has been configured for a selected persona, a user belonging to that persona will only be able to view the glossaries curated through glossary policies.
• If a user is not part of any persona, they will be unable to view any glossaries in Atlan.
• If a user is part of a persona that does not have any glossary policies or any policies configured, the user will be unable to view all glossaries.
• The restriction will be applicable to the Assets page, glossary tree, terms filter on the Assets page, terms in an asset sidebar, linked assets, and related terms.

👏 Give it a shot

Switch to better curation of your glossaries today by turning on the Labs toggle. And as you try it out, let us know what you think! Learn more: How to restrict glossary visibility.

🎉 What's new

You can now use Atlan AI to generate READMEs for your glossary terms! This provides you with an excellent starting point for documenting business context. Once generated, simply review and edit the Atlan AI-generated README and then add it to your glossary term.

Note that you will need your admin to enable Atlan AI in your Atlan workspace to use this feature. If Atlan AI is already enabled, get started right away!

🎉 What's new

Building on the success of exporting assets to spreadsheets, Atlan now supports exporting impacted assets to Google Sheets and Microsoft Excel! The impact report also includes additional fields for usage, popularity, impacted asset type, and more, ensuring a greater impact on your impact analysis.

✨ Let's dig deeper

Once your Atlan admin has integrated a supported tool, you will be able to export impacted assets to spreadsheets. Your existing permissions and access policies in Atlan will determine whether you can export the impact report, but at a minimum you'll require read permission on the assets you want to export.

In addition to downloading the impact report in a CSV file or as an image, Atlan now supports exporting the impacted assets report to:

• Google Sheets
• Microsoft Excel online

👏 Give it a shot

From exporting your impacted assets to better understanding the flow of data right from the spreadsheet, you'll never miss a beat! Note that Atlan currently does not support updating asset metadata in the spreadsheet and syncing impacted assets back to Atlan — coming soon!

Learn more:

• How to download and export lineage
• How to export assets

🎉 What's new

Atlan now supports reverse sync for imported Databricks tags! You can now import your Databricks tags from your Unity Catalog-enabled workspace to Atlan, update your Databricks assets with the imported tags in Atlan, and push the tag updates back to Databricks.

Tags from Databricks can be synced both ways — Databricks 🔁 Atlan.

✨ Let's dig deeper

Once you have imported your tags from Databricks and granted the required permissions, you can turn on reverse sync for your Databricks tags in Atlan. This will allow any updates to the tag, such as attachment on an asset or an update to the tag value, to be synced from Atlan to Databricks.

👏 Give it a shot

Learn more about Databricks tag management here:

• How to manage Databricks tags
• How to set up Databricks
• How to crawl Databricks
• How to attach a tag
• What are tags?
• How to use the filters menu

Please note that this feature will be a paid addition. Reach out to your customer success manager for more information.

🎉 What's new

Atlan now supports workflow alerts for custom packages! If you have set up any custom packages on your Atlan instance, you will be able to monitor your workflows directly in Slack or Microsoft Teams. As a prerequisite, you will need to configure your Slack or Microsoft Teams integration settings to receive workflow alerts from Atlan.

🎉 What's new

Introducing event logs for your OpenLineage events in Atlan! This events observability dashboard can help you monitor your events and debug any issues. You'll never have to wonder about what happened to your OpenLineage events sent to Atlan!

Note that you will need to be an admin user in Atlan to view event logs from the admin center:

• View a list of up to 20 most recent events received from OpenLineage.
• View the timestamp, connector name, and JSON code for each OpenLineage event.
• Filter events by supported connectors — Airflow (also includes all other supported distributions, Amazon MWAA, Astronomer, and Google Cloud Composer) and Apache Spark.

Learn more: How to view event logs

🎉 What's new

Keeping this short and sweet, two enhancements to improve your lineage experience in Atlan:

• The display of long asset names has been enhanced for better readability. You can now view the first and last few characters in the name to help you distinguish between your objects.
• You can also view the bucket name for your GCS or S3 partial asset objects on the lineage and pipeline graphs.