Dynamics Community Forum Thread Details

Power BI Report Issue

HI All,

We are facing the below error message while trying to open a PowerBI report in "Customer Credit and Collection" workspace where as this report is loading for user with "System Admin" role.

The role which has a view access for this report is "Collection Manager". We have assigned this role to the user but he's getting the below error.

Cannot load model

Couldn't load the model schema associated with this report. Make sure you have a connection to the server, and try again.
Please check the technical details for more information. If you contact support, please provide these details.
Hide details
Underlying ErrorPowerBI service client received error HTTP response. HttpStatus: 503. PowerBIErrorCode: OpenConnectionError
OpenConnectionErrorFailed to open the MSOLAP connection.
Correlation IDceb911e3-be41-56bd-a600-5a91c8fa420d
Activity ID370442a6-2918-4f01-98ce-9e51caab1c61
Request ID583610e9-52cb-4d18-8f88-e9d6d01ebb83
TimeWed Apr 27 2022 18:04:00 GMT+0530 (India Standard Time)
Service version13.0.18129.59
Client version2204.3.11090-train
Cluster URIWABI-WEST-EUROPE-E-PRIMARY-redirect.analysis.windows.net
Activity ID370442a6-2918-4f01-98ce-9e51caab1c61
Request ID583610e9-52cb-4d18-8f88-e9d6d01ebb83
TimeWed Apr 27 2022 18:04:00 GMT+0530 (India Standard Time)
Service version13.0.18129.59
Client version2204.3.11090-train
Cluster URIWABI-WEST-EUROPE-E-PRIMARY-redirect.analysis.windows.net

Did anyone faced the same error?

Regards

Namita

Hi,

As per our understanding, you are facing an issue while opening a Power BI report embedded in the “Customer Credit and Collections” workspace, where the report loads correctly for a System Administrator but fails for a user with the Collection Manager role, showing the error “Cannot load model / Failed to open the MSOLAP connection (HTTP 503)”.
This is actually pretty common in embedded Power BI scenarios in D365 Finance & Operations. It usually comes down to permissions and licensing, not a problem with the report itself.
Here’s what I’d check, step by step:
Why does it work for the System Admin?
Basically, the System Admin role skips a lot of the behind-the-scenes security checks that normal business roles go through. So a Collection Manager needs to have all the right access set up.
Step 1 – Check Power BI Licensing
Make sure the affected user has either a Power BI Pro license or access to a Power BI Premium capacity. Without one of these, they won’t be able to connect to the dataset, and that’s often what causes the “MSOLAP connection” error.
Step 2 – Add the Right D365 Finance Roles
The Collection Manager role alone usually isn’t enough to access the data behind the report. Try adding one of these additional roles in D365:

Accounts receivable clerk
Accounts receivable manager
Credit and collections manager
Power BI user (or a similar analytics role)

Step 3 – Make Sure Power BI is Enabled for the User
Go to System administration > Users, open the user’s record, and check that Power BI enabled is set to Yes.
Step 4 – Confirm Legal Entity Access
Double-check that the user has access to the same legal entity (company) as the System Admin who can view the report. Also, make sure they have a valid default company set.
Step 5 – Refresh Security (if nothing else works)
Sometimes permissions get cached. If you’ve made changes and it’s still failing, try: