Forum Discussion
Getting a token error on PowerBI Embedded Report that is using SSAS on-premise data source with RLS
Yes the token error comes up when viewing the report (please see attached).
This doesn't look like an error from Power BI side. Can it be from your BE code which fails to generate the token?
You should open network traces to see what's failing and/or debug BE code to see what is failing and why.
Sorry, what's BE code?
No changes to the codebase on the front-end. And no changes to the token lately either.
And I have another Semantic SSAS Model with identical RLS (Row-Level Security) that connects just fine to those embedded reports. No token error whatsoever.BE means back-end.
I guess you have a code where you actually call Power BI API to generate the embed token. Is this API call successful? Do you get an error there? Without traces that shows requests being sent to Power BI and fail it's not possible to help.
"Error getting report token" is not an error printed by Power BI side. It comes from your code. You should know how to debug your code to see where it fails, and if it fails because of an error returned from Power BI you will have to try and see that error message you got from Power BI, it might have useful information to understand the reason.
Ok first of all, learn to communicate using plain language. Nobody abbreviates BE or FE when referring to Back-End and Front-End.
No changes to our front and back-end architecture/codebase. The only change made was in the semantic SSAS model. And the change had no impact nor anything to do with the RLS (Row-Level Security).