Jordan
Jordan
This is a bug in the API and the service - if you look at the lineage view for datasets using PowerPlatform.Dataflows it's also broken there.
You'll see this if there's a "corrupted" dataset in your tenant where Power BI can't find the data sources for some reason. Unfortunately fixing this would be a big project...
The Apps As Admin REST APIs don't include Workspace ID, and really Apps are related to Reports, not workspaces. And while I'm sure that the workspace-level APIs return the appId...
Thanks! An yes, technically apps are related to workspaces but only indirectly, through reports and dashboards in the workspace. In the REST API, the appId foreign key is only present...
Sorry for the delay on this, i've been out on parental leave until this week. Thanks so much for contributing! A few notes: The main problem I see with this...
This was fixed a while ago by Microsoft - there's still an issue with Upstream Dataflows using PowerPlatform.Dataflows() as reported in #145
It is, the field is called appId and just needs to be added to the record expansion for both dashboards and reports.
Closed with #146
This is a known issue with the Power BI REST API itself. Lineage between dataflows is broken both in the API and the lineage view in the Power BI Service...
If you're in a larger tenant there's a chance that API call will timeout or your token will expire since it has to loop through every dataset in the tenant...