One way MyDataWork makes a difference in your data work
You build dashboards in Power BI. That’s your primary surface for the work that matters — the executive KPI views, the regional sales drilldowns, the operational dashboards leadership checks on their phones. Power BI gives you a lot. The Lineage View in Power BI Service shows you the dataflows feeding your semantic models, the registered external sources behind those dataflows, and the reports and dashboards downstream. With Microsoft Purview and Fabric, that lineage extends further across hybrid, multicloud, and on-premises sources, with strong governance over assets that have been registered and scanned.
That stack is genuinely valuable. The question is what it captures, and what it doesn’t.
Your Power BI work doesn’t exist in isolation. There’s the Alteryx workflow that prepares the analytical dataset before it lands in your Power BI dataflow. The Tableau dashboard a parallel team built against the same source data, uncoordinated. The Excel model your business partner maintains and refreshes manually each week, which feeds a CSV that lands in OneDrive and gets picked up by your dataflow. The Snowflake table that’s part of an upstream pipeline. The Python notebook where your colleague validated the methodology before any of this got built. The stakeholder spreadsheet capturing who depends on each report and for what decision.
Power BI gives you strong visibility into Power BI workspace lineage and registered dependencies. Purview gives you strong governance over assets that have been catalogued and scanned. Both are built for the governed, admin-managed view of your data estate. What neither was designed to capture is the broader analyst work context — what the dashboard is for, who depends on it, what outcome it supports, and the often informal, file-based connections to artifacts that live outside the governed catalog: the Excel models, the local CSVs, the Python notebooks, the Tableau workbooks, the stakeholder docs.
That’s the gap MyDataWork fills. It catalogs your .pbix files alongside the Alteryx workflows, Tableau workbooks, Excel models, Python notebooks, Snowflake tables, GitHub repos, and dbt models that surround them. Using asset metadata and connection signals — without analyzing business data inside the files — it infers multi-hop lineage across all of them, so you can see a Power BI dashboard, the Alteryx workflow that prepared its dataset, the SQL staging step in between, and the Snowflake source table behind that, all in a single explorable graph. Adjust the depth to show one level of connections or several. Click any node to refocus the view on that asset and walk the lineage outward from there. Zoom, pan, and export the graph as an image when you need to share it with stakeholders.
Lineage inferred from asset metadata and connection signals across Snowflake, SQL, Alteryx, Excel, and Power BI — one explorable graph, with adjustable depth and click-to-refocus.
Lineage is one piece. Around it, MyDataWork lets you document — in the same workspace — the use case each dashboard supports, the stakeholders depending on it, the measurable business outcome it serves, and the progress toward that outcome. The agent surfaces observations a human might miss: a Power BI file that’s become hidden infrastructure across multiple use cases, a recently-added asset nobody has linked to documented work yet, a use case with no stakeholder assigned.
Agent observations across the workspace: a Power BI file referenced across multiple use cases, a new Excel asset that pattern-matches an existing use case, and a use case missing a stakeholder.
MyDataWork doesn’t replace your governance stack. It sits alongside it, focused on the working layer — the practitioner’s view of which assets connect to which decisions, who depends on what, and where the business value lives. The use case for a Power BI-centric analyst is direct. Stop spending time reconstructing context every time someone asks an impact question that crosses tool boundaries. Have a single record of your dashboard ecosystem, the work around it, and the business outcomes it serves — including the work in tools your governed catalog wasn’t built to track.
A use case in MyDataWork: objective, target outcome, and baseline-to-target progress — documented alongside the assets that support it.
A 90-day free Explorer plan gets you started now. No credit card. Bring your email and you’re working in minutes.