How to retrieve both proxy- and core-dataset IDs to generate an embed token for a DirectQuery

[Himanshu_G]

I have a Power BI report built on a proxy dataset (used for row-level security, parameterization, etc.). That proxy dataset in turn is created on top of a core DirectQuery dataset. In order to generate an embed token for the report, I need both:

1. The proxy dataset’s ID (so I can call the GenerateToken endpoint with the right dataset)

2. The underlying core dataset’s ID (so that DirectQuery queries actually run against the real model)

What I’ve Tried

• Using GetReportInGroup to retrieve the report metadata. This returns the proxy dataset’s GUID but provides no indication of the core dataset’s GUID.

• Calling GetDataSourcesInGroup on the proxy dataset to inspect its data source connection details. While I can see that it’s pointing to my AnalysisServices endpoint and database name, there’s still no dataset GUID exposed.

Questions

1. Is there a REST API endpoint or property on one of the existing endpoints that returns the core dataset’s GUID, given only the proxy dataset’s GUID?

2. If not, what’s the best practice to programmatically discover that core dataset ID in a fully automated (non-manual) flow?

Thanks in advance for any pointers!

[andrewsommer · Accepted solution]

No, there is currently no REST API endpoint that directly returns the underlying/core dataset ID (from a DirectQuery for Power BI dataset) given only the proxy dataset ID. The metadata is internally present, but not surfaced via the public Power BI REST API.

Please mark this post as solution if it helps you. Appreciate Kudos.