Forum Discussion
Embedded reports built over multiple XMLA datasets stopped to work after weekend update
Dear community,
starting from March, 6 potentially after some weekend update
all our PowerBI embedded reports that are built over multiple datasets
in multiple applications running in multiple zones over different embedded capacities,
all stopped to work.
Example goes below:
Activity ID: 88571e51-cf7a-43bd-8be6-787fc37f282f
Request ID: a86974e9-794d-4300-a076-dc4acb43aefe
Correlation ID: 4e1ec105-2476-bd3f-5b87-ac292f2b2ba3
Time: Tue Mar 07 2023 08:29:51 GMT+0200 (Eastern European Standard Time)
Service version: 13.0.20195.63
Client version: 2302.4.12605-train
Cluster URI: https://WABI-WEST-EUROPE-redirect.analysis.windows.net
Activity ID: 88571e51-cf7a-43bd-8be6-787fc37f282f
Request ID: a86974e9-794d-4300-a076-dc4acb43aefe
Time: Tue Mar 07 2023 08:29:51 GMT+0200 (Eastern European Standard Time)
Service version: 13.0.20195.63
Client version: 2302.4.12605-train
Cluster URI: https://WABI-WEST-EUROPE-redirect.analysis.windows.net
A years ago we experienced the same when we just started embedding and that time it was missing
XmlaPermissions: ReadOnly
in our generate-token request.
We still have this code in place,
but it looks like our embed token generated currently is missing these XmlaPermissions.
Any ideas how to investigate the issue ?
Thank you,
Illia
4 Replies
Also wanted to clarify - we follow `Embed for your customers` flow with using of `Service principal`
Hi Illia,
I have the same issue (I think), since yesterday our Embedded reports aren't working. I've tried just about everything but I can't find a solution. Did you get anywhere?
Best,
Joery
No, opened a support ticket with Microsoft.
No solution yetOke thanks, I've raised a ticket as well.
At least I do feel better knowing that I'm not the only one having this problem.
