Forum Discussion
Problem embedding report - "This content isn't available"
Thanks for your reply, eligr. To answer your questions:
- Yes, I have a Power BI Pro trial license.
- Yes, I can log into powerbi.com and view these reports.
- Yes, my appliction has been granted all the available Power BI permissions in the Azure app registration. It also has a few of the Windows Azure Active Directory permissions.
To provide some additional context, my application is successfully authenticating and getting access to the Power BI API after following the guidance here. I retrieve the available groups through the API, and then retrieve all the available reports and dashboards within those groups. My application then displays that information on a web page with the report/dashboard title hyperlinked. The hyperlink opens a new browser window and attempts to embed the report/dashboard content using the powerbi.embed function and the embed URL retrieved from the API.
One thing that is confusing to me is that I keep coming across references to embed tokens, but it's not clear to me under what use cases I have to use an embed token. The embed samples that I referenced in my original post do not use an embed token. I looked at the troubleshooting page that you referenced in your reply, but none of that seems very applicable since all of my API calls are succeeding in the C# code. It's only in the powerbi.embed call that I have a problem. What can you recommend to debug this further? Thanks again for your help!
Having recently waded through this labyrinth of configuration, I'll share the parts I got stuck on in hopes that they help you find your solution:
- embed tokens are only required if you're using the Premium capacity approach. Premium capacity is required if your end-users (that is to say, the people viewing your embedded content) do not have Power BI Pro licenses and are not a part of the Power BI Workspace that is hosting your datasets, reports, dashboards, etc. If your users have their own Pro licenses (sometimes the case if you're sharing internal data with colleagues) and are a member of the source Workspace, you won't need an embed token - JUST your access token. (It sounds like you're up to speed on access tokens, but let me know if I can expand on those.)
- the bug that plagued me right up until I got embeds working was the TYPE of authentication I was specifying in my request. I'm taking the Javascript route, but you should be able to figure out what the C# equivalent is:
var models = window['powerbi-client'].models;
var config = {
type: 'report',
tokenType: models.TokenType.Aad,
accessToken: accessToken,
embedUrl: reportEmbedUrl,
viewMode: models.ViewMode.View,
id: reportId,
};Every example I found here and elsewhere on the internet was using "tokenType: models.TokenType.Embed" - which is intended for use with the method I described above. I was using the Active Directory Authentication Library (adal.js) approach, which checks the user's browser for existing AD sessions (recommended for the end-user-has-Pro-license approach). When I finally tried dumping "models" to output and saw the parameters model.TokenType accepts, it all came together.
Happy to share my working code if you think it will be of use, but hopefully the above will get you started toward the right solution. Good luck!