This message was deleted.
# secoda-supportw
wooden-spring-14915
02/17/2022, 7:08 PMThis message was deleted.
e
elegant-house-93198
02/17/2022, 7:37 PM
Hey @blue-ocean-91219 I’d love to hear how your team is pulling this lineage information from the Power BI API. We could apply that to our extractors to get the end-to-end lineage going for you.
When we made the PowerBI integration I couldn’t find any information related to the connections between datasets and the source tables from snowflake. If we have that information it’s very straightforward to add it to the Secoda product.
b
blue-ocean-91219
02/17/2022, 8:51 PMHi @elegant-house-93198, so we're using the Power BI Admin API's Metadata Scanning feature. This does have to be enabled by the Power BI admin to start collecting metadata.
blue-ocean-91219
02/17/2022, 8:51 PMblue-ocean-91219
02/17/2022, 8:54 PMThese scan results include a "tables" object inside of a dataset object, which includes table names and a "source" expression that provides the snowflake connection details, database, schema, and table name.
blue-ocean-91219
02/17/2022, 9:03 PMThe "source" expression is the raw Power Query
e
elegant-house-93198
02/17/2022, 9:05 PM
This is helpful context, I did see they recently released the scanner API and haven’t gotten the chance to explore it further. So it’s good that you’ve actually accomplished getting lineage information so that makes me optimistic we can do it as well.
👍 1