---
title: "Lineage: Impact Analysis Through the UI"
url: "https://atlan.com/demos/impact-analysis-through-the-ui/"
description: "Ensure proposed data changes won't cause issues with Atlan's impact analysis, quickly identifying affected assets and who to contact for approvals."
format: "Video"
video: "https://videos.ctfassets.net/nwa1c00rtgxb/62YEjKEmqwsjR5OK0VpqaA/53a3a687699fc0188ea2e922fbf44fab/Impact_analysis_through_the_UI.mp4"
content_purpose: ["Product Overview"]
target_persona: ["Data Engineer"]
journey_stage: ["S2 - Discovery", "C4 - Expansion"]
use_case_context: ["Training"]
product: ["Enterprise Data Graph - Data Lineage"]
content_type: "video transcript"
transcript_source: "contentful"
---

# Lineage: Impact Analysis Through the UI

Transcript of the video at https://atlan.com/demos/impact-analysis-through-the-ui/

<!-- Body: machine transcript stored on the Contentful entry (field contentBody), timestamps kept, product names corrected. Not yet edited by a person. -->

Impact analysis through UI

[00:00]

Steven Hloros: In this walkthrough, we will be using Snowflake as our data warehouse and Tableau as our B I tool. Just by setting up the native connectors, Atlan auto generates the lineage needed for Impact Analysis for applicable connections. This lineage actually goes down to the column level inside of Snowflake, like many other SQL assets inside of At-lin.

We will start this Impact analysis process as the data producer that is making the change. The change planned is to modify the calculation of the days since prior order column. There are four different ways that At-lin can improve your impact analysis process when implemented.

The first is through At-lin and the lineage U I itself. We will start by going to the table asset where we are making the change. By clicking on the lineage tab, we can see the visual representation of the lineage. Initially we start at the table level. When opened, lineage will show for one layer upstream and downstream. We can click on the plus icons to move upstream or downstream from the starting asset. The asset that we start with will always keep a home icon above it, as knowing exactly how to get back to where you started can be critical when dealing with complex and vast [01:00] lineage. We can also quickly expand to see all upstream or downstream assets by clicking on the expand all icon.

Now since the changes being made are at the column level, we can see this lineage by simply clicking on the View fields hyperlink. When this is clicked, columns from our table will show. By default these will show in alphabetical order, but by clicking on the eye icon on the upper right hand navigation, we have the ability to switch the order to our preference. In this case the days since prior order column appears right away, and by clicking on it, we can now see the upstream and downstream lineage of this column. As shown here, the days since prior order field flows not only into a tableau data set, but also into other Snowflake tables and additional data sets. As we look at our lineage, it may be something that we want to share with others in a visual representation as we do the analysis. By simply clicking on the picture icon, a download of the lineage will be generate so that it may be shared offline. When there are only one or two downstream assets, the visual lineage can be a great way to quickly identify and key in on all your downstream impacts. However, when you have a more complex data structure like this one, [02:00] the impact analysis report can be much more useful. Clicking on the view impact report will give us the downstream assets we are looking for, along with key metadata that can assist us in our impact analysis, such as the owners of downstream assets. As the data producer we now easily able to see all assets that may be impacted by our change. From here, we can create tickets on each of those assets and assign them to the owners through the native jira integration, create slack or teams messages directly from Atlan to the owners to notify them of the impending modification, or communicate outside of Atlan with those users of the modification. With just a few clicks we were able to identify the impacted assets and who to contact on the changes. Along with a good workflow process for approvals of the changes from those impacted, we quickly ensured that the proposed change will not cause issues.