Forum Discussion
Error generating an embed token with a composite model
We have a Power BI Embed application for a number of reports. Recently we added a report to our embed application that points to a composite model. When we do that, we get the following error:
message=RDL Report cannot connect to dataset xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx because XMLA permissions are off
I've tried the following so far.
- Verified the report works directly inside the Power BI service
- Verified I can connect via XMLA to the composite model
- Ensure the service principal used by the embed application has access to both datasets
- Ensure the service principal used by the embed application has access to both workspaces
- Updated GenerateTokenRequestV2 to include both sets of dataset ids and workspace ids instead of just the dataset and workspace the report is directly pointed to
- Verified we weren't violating any published limitations under: https://docs.microsoft.com/en-us/rest/api/power-bi/embed-token/generate-token
Is there anything else anyone can think of? Is this a known limitation?
Thank you in advance!
KevinSnow when you say that you have "A connection to a global dataset ..." I believe this is what the limitation refers to as "DirectQuery connection to a Power BI datasets". Your first dataset is connected to the second dataset in direct query mode (regardless of the fact that they reside in different workspaces).
This limitation in Power BI embedded is expected to be lifted in a few weeks, but currently it's not supported.
8 Replies
KevinSnow what does your composite model connect to and how is it connected?
It's possible that your scenario isn't yet supported by Power BI embedded.
For example there's this limitation documented:
Using Power BI Embedded with datasets that include a DirectQuery connection to a Power BI datasets or Azure Analysis Services model isn't currently supported.
Most limitations regarding embedding a report with composite models are due to be removed in the comming weeks.
Interesting. If you have a Pro license you can consider raising a Pro ticket at https://powerbi.microsoft.com/en-us/support/pro/ . Curious to hear what they have to say about this.
The composite model contains two parts
1) A small internal dataset that is populated based on report parameter values
2) A connection to a global dataset in a separate workspace. The global dataset is refreshed nightly and contains a long-running pull from Azure Blob Storage. It goes directly to the blob account and not through a gateway connection.I did not find where the case we are trying to perform is listed as a limitation, but maybe I missed it?
lbendlin - I will look into getting a support ticket created for this if it's not something that is under a known limitation.
KevinSnow when you say that you have "A connection to a global dataset ..." I believe this is what the limitation refers to as "DirectQuery connection to a Power BI datasets". Your first dataset is connected to the second dataset in direct query mode (regardless of the fact that they reside in different workspaces).
This limitation in Power BI embedded is expected to be lifted in a few weeks, but currently it's not supported.
AmosHersch Do you have an updated ETA on the lifting of this restriction as it is still in place.
