Forum Discussion
Advocate I"PowerBINotAuthorizedException" error when using public Url EVEN after removing imported tables
Hi all, I seem to have found a solution by using Windows PowerShell in order to use Power BI REST API commands. I was able to "rebind" (official term) an existing report to another "non-corrupted" source / semantic model. The whole thing took 3 command lines and only 1 minute!
Finally a solution after wasting a week working between Power BI Service, Desktop, unzipped PBIX files... 🙂
Here are:
- the Reddit post on which I found some information: https://www.reddit.com/r/PowerBI/comments/1dc7wsu/changing_the_semantic_model_for_an_existing/
- more documentation on the Rebind command: https://learn.microsoft.com/en-us/rest/api/power-bi/reports/rebind-report-in-group
Let me know if anyone else has also fixed this kind of problem by using the Power BI API.
Regards, Olivier.
Hi oduc78 ,
According to your description, in Desktop I added more tables by importing them from another semantic model and then published them to Service.
The error you are experiencing is reproduced, so it means that it is not possible to publish to the web in this way.
So please check your report to make sure it is not an unsupported type. For example:
- Reports that use row-level security.
- Reports that use DirectQuery to connect to data. Reports that use DirectQuery to connect to data. connect in composite or import mode instead.
- Reports in a workspace where you are not an editor member.
- Single sign-on data query model.
- Protect confidential or proprietary information.
- ...
More detailed information can be found in the documentation:
Publish to web from Power BI - Power BI | Microsoft Learn
Best Regards,
Clara Gong
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
oduc78Thanks a lot Clara Anonymous for your reply! 👍
As I wrote, I am aware that live connected tables from another semantic model prevents from publishing on the web with a public URL, that's why I'm just trying to revert all my changes and remove any live connected data or anything that causes this blockage.
I tried to start from scratch again today with just a hand-typed, 4 rows table, no connection whatsoever, and when I publish this report with the name of my original report and overwrite it, I'm still not allowed to publish on the web. 😥
It's like all the reports using my semantic model are been "flagged" as "not eligible" regardless of the name or content of the semantic model.
Any idea?