Forum Discussion
Viewing Scorecard in App
Hi aelsken ,
Based on the details you have provided, you seem to have taken the correct initial steps.
Can you make sure that the scorecard has been shared correctly with the users. For more information, please see:
Create scorecards and manual metrics - Power BI | Microsoft Learn
At the same time, can you provide more details about the error messages? For example, details and screenshots of error messages encountered by users, whether the problem exists for all users or for a specific user.
Best Regards,
Ada Wang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- aelsken2 years agoFrequent Visitor
Thanks for the responce. It was my impression that you do not need to share when publishing to an app just like a report, is this not the case with scorecards? I have contributor role in the workspace but I can only share to people with existing access. When I use the share with existing users link, they still get the same error. I have contacted my admin on that reguard. As for the error:
Activity ID: c58d6296-03ed-40e2-8c74-2551b653bab4
Request ID: a25d2308-4543-5572-077e-da177d952fb1
Correlation ID: 95be7c6f-28d6-e5df-c8e0-df4eab6eb561
Time: Tue Apr 30 2024 08:10:35 GMT-0700 (Pacific Daylight Time)
Service version: 13.0.23120.63
Client version: 2404.3.18977-train
Cluster URI: https://wabi-us-gov-tb-texas-redirect.high.analysis.usgovcloudapi.net/ - jpmuk2 years agoFrequent Visitor
Same issue in my organisation.
> Scorecard set up
> Included in App Content
> App Published
Users get the same "something went wrong" error.
All Users selected have app access to all other reports from where the scorecard sources it's data from
The users can only see the scorecard if they are either added into the workspace (undesirable for many reasons), or if the scorecard is manually shared with them (needless duplication of access rights).
The scorecards should allow access exactly the same as all other aspects work at app based permission.
This feels like an oversight/bug unless I'm missing something obvious, but I can find posts about this issue going back to 2021.