Power BI Embed Problem

[Rick4him]

Power BI Embed web page been up for nearly a year.  All reports worked fine until a few weeks back.  Embedded model is user owns data.  All new reports added to workspaces and shared out, get loaded by name after call to PBIReports Reports = JsonConvert.DeserializeObject<PBIReports>(reader.ReadToEnd()); but when requested to render the report, 1st a Power BI Logo appears in middle of window as usual, then a message Checking Permissions... this may take a few minutes, then "This content isn't available. Learn More about Power BI"  (see insert below).  The web page continues to render any older report but will not render any new report.  If you modify an old report that works and then publish back to the same workspace with replace, it continues to work, however if you change its name and publish it to the same work space and share, it will get the error.  Very strange. All workspaces are covered by Premium, not that it matters as I am a Pro User.  All reports in all work spaces work as intended on app.powerbi.com.  Many of these are also used in publshed to web forum and this also works for old and new reports. Only those reports that have been added new recently to any workspace do not work in the Embedded API web program.

[v-juanli-msft]

Hi @Rick4him

Reference may helps you.

https://community.powerbi.com/t5/Developer/Problem-embedding-report-quot-This-content-isn-t-availabl...

https://docs.microsoft.com/en-us/power-bi/developer/embedded-troubleshoot

If it doesn't help, I would suggest you open a ticket to get help from MS senior engineers.

Best Regards

Maggie

[Rick4him]

I reviewed those topics prior to submitting issue.  The issue is different as the individual did not have a working embed application and I have had mine up for nearly a year.  The issue I am having is that it will not work on any new PBIX reports.  It works fine on all the older ones even if the older ones are modified.  It will not work on any new report even if that report is based on one that works as in the name is changed and it is published, the original continues to work and the new renamed copy does not work.  That makes no sense.  It does not appear to be the desktop application injecting something that embed API does like as it can modify an older report and re-publish (replace) and that report will continue to work.  Only newly named reports do not work as if there is a limit in how many can work (ridiculous) or that the infrastructure has changed in a fashion that  when a new space for report is allocated it does not work in the embed API (somewhat logical).