Forum Discussion
Table level or Columns level lineage
Hallo Community,
is it possible to trace the source tables and columns used in a report?
I understand that intermediate transformations can change the tables and columns during the process. However, I would like to know if there is any workaround or best practice to trace the fields in a report back to their original source tables and columns.
We are having Medallion architecture and using Noteboos (pyspark) to transform the data.
Any tips or suggestions would be greatly appreciated.
5 Replies
- EduardoCastroNew Member
Hallo,
Yes, it is possible — and the fabric-toolbox repository provides a ready-made solution for this exact scenario.
Microsoft's fabric-toolbox includes a Lineage Extractor notebook that automatically extracts column-level metadata from Fabric artifacts and uploads it to Microsoft Purview to create a graphical lineage graph.
You can take a look at
https://github.com/microsoft/fabric-toolbox/tree/9dcbc14496f4f6342f3af1f482073ff0be0d91e0/tools/Lineage_Extractor
- Kuladeep
Advocate II
I think this works solution upto some extent of our usecase. I will test this and get back here
- Murtaza_Ghafoor
Super User
Hi Kuladeep,
Recommended: For table level lineage use Fabric Lineage view.Fabric can provide lineage across items such as:
Source → Bronze → Silver → Gold → Semantic Model → Report
This is the easiest way to understand dependencies between tables, notebooks, semantic models, and reports.
If you need column level lineage then you need to build meta data table across your workflow, this is where things will become difficult.
you can create this by using DAX studio butHowever, DAX Studio will not give you complete lineage back through your PySpark notebooks, it will only limit up to sematic layer, for lineage back to pyspark you must create techinal meta data table in your workspace using pyspark. Something like this
Target LayerTarget TableTarget Column Source TableSource
If this helps, ✓ Mark as Kudos | Help Other