Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I have seen a strange behavior today and am not sure if it has always been like this or not.
If I build a paginated report on top of a dataset where both are in the same workspace, this API call (that is great for lineage)
https://learn.microsoft.com/en-us/rest/api/power-bi/admin/workspace-info-post-workspace-info
returns this (which includes the dependentOnArtifactId so we know which dataset it is connected to)
but... if the report is in a different workspace than the report, it returns this:
nothing to show, no dataset id or anything... no way to figure out which dataset it is connected to.
Please remember this API call is for tenant admins so it does not matter what my personal access to any workspace is.
Microsoft has fixed this somehow
Hi @Brunner_BI
You can refer to the following documents:
Run metadata scanning - Microsoft Fabric | Microsoft Learn
Admin - WorkspaceInfo PostWorkspaceInfo - REST API (Power BI Power BI REST APIs) | Microsoft Learn
Best Regards,
Yulia Xu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks but all of these settings are ON.
Like it says above, it is getting it for the same dataset if the Paginated report is in the same workspace as the dataset.
Just not if the report is in another workspace which seems like a bug to me.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 56 | |
| 55 | |
| 32 | |
| 18 | |
| 14 |