Hello Community,
ic
I have been refining already existing datasets and in the process of doing so have to spend time looking at which analysis/dashboard is currently using the dataset and which fields are in use directly and which fields are referenced in calculated fields. This takes time.
Is there a way to determine the dataset fields that are referenced in analysis/dashboards?
There is a custom solution developed by senior members on my team outlined in this blog post.
A Quick Sight dataset can be reused across many analyses and dashboards. One advantage of creating centralized, reusable datasets is that changes to the data within a dataset will be applied to multiple dashboards. This reduces the maintenance efforts compared to managing individual datasets for each dashboard.
Nevertheless, it is important to consider the potential effects on connected analyses and dashboards when modifications are made to the dataset. Therefore, it’s crucial to understand how datasets and data fields are used across various analyses and dashboards when considering the impact of making schema changes. Tracking column-level lineage provides a clear view of each column’s path through different parts of Quick Sight.
This insight helps optimize data processing, improve query performance, ensure accuracy, and meet regulatory requirements. A good data lineage solution shows exactly how data moves and is used, helping organizations make better decisions. It also helps identify and remove unnecessary data fields from Quick Sight SPICE, speeding up data ingestion, saving space, and simplifying data pipelines. Better visibility into data lineage leads to improved data governance and regulatory compliance.
In this blog post, they explore how to create a simple serverless architecture using AWS Lambda, Amazon Athena, and Quick Sight to establish column level lineage.
I don’t see any the items you mentioned in this response. If I go to datasets and open a dataset, I can see what analysis and dashboards are using it (and users who have access to the analysis and dashboards), but can’t see nearly the level of detail you describe above. I am an admin on our system.
I have attached what I can see. Is there a different version or access point to see the visual representation of our dataset schema?
We have been struggling with the same question and I hope I can use your solution above!
Hi @Giridhar.Prabhu,
It’s been awhile since we last heard from you, did you have any additional questions regarding your initial topic?
If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.
Thank you!
@Brett it seems as the solution recommended above by @murili is limited only to the AWS Quick Sight Console. Is there a plan to implement a similar feature in the data set authoring screen for non-admin users?
Hi @Brett,
You can go ahead and close the topic.
Hi @BrianJager,
I’m unsure on the current roadmap for feature updates set by the AWS team but I can set as a feature request to add to their radar.
