Power BI desktop Read only access to SSAS MD cube

[cyclist007]

Hi,

I created reports in Power BI desktop connecting to a live SSAS cube (I am an admin on the SQL server where the cube resides). The desktop file works fine for me. When I share these Power BI desktop reports with a colleague (edit: via email) who has read only access on the cube, he cannot open PBIX file - it gives the error 'Model does not exist'.

Do all Power BI desktop content viewers/consumers need to be Admins on the SSAS server (or what kind of role on the SSAS server does my colleague need to be in)?

[dkay84_PowerBI]

When you say "share" you are emailing or otherwise sharing the actual PBIX file (as opposed to the online service)?

When they open the file, have they gone to the Data Source Settings menu and updated the credentials?

[cyclist007]

When I say share I mean emailing the file.

When they try to open the file, they are allowed to edit the connection (that is enter server name & cube name), on entering the server name they get an error no models exist. They could access the cube through management studio, but not through Power BI ... does Power BI desktop report need the user to have more than read-only access to the SSAS cube (and why?)

[dkay84_PowerBI]

Have them try going to the Data Source Settings menu (Home tab > Edit Queries drop down arrow > Data Source Settings) and go to the Edit Permissions menu.

See if they can update their credentials and gain access.

[cyclist007]

I dont think the file opens at all for them to go to the Home tab and update their credentials. And we are using a Windows AD account hence what else should they update? 

[dkay84_PowerBI]

The PBIX should open and just give an error message for the data source being unavailable (i.e. charts/visuals will display error message and Query Editor will give error messages for the queries).  If they can't even open the file that sounds like more of an IT issue or something related to their specific machine specs.

[cyclist007]

They can easily open a normal PBIX file. But they cannot open  the file which has data live connected from an SSAS cube (which they have only read-only access). It basically stops them showing a connection error (model does not exist).

[CahabaData]

I haven't had the opportunity to connect to an SSAS cube; but generically speaking - any live link requires credentials that are relative to the location of the pbix file.  Contrast this with a Get Data (not live) that imports the data into the pbix file - you can share the file freely because the data is contained within.  So I believe what the other posters are saying is that they must re-establish their linking credientials.

Of course potentially the better approach is to publish it up to the PBI Service and have them review the report there - so they do not have to have SSAS credentials.

[cyclist007 · Accepted solution]

We found the solution .... the read only access has to be explicity given not only for the SSAS server but an individual entity levels, that is including the cube level (the initial assumption of providing read only access at the high level did not suffice). After that he could not connect to the cube and view the reports. 

We are not allowed to use Power BI service (cloud), so that is not an option. 

[dkay84_PowerBI]

You should consider Power BI Reporting Server which provides the same collaborative functionality (more or less) as the service but is entirely behind your company firewall (on premises)

[cyclist007]

Yes, but its just announced so will look into in the future. Also need to consider IT approvals & cost-effectiveness. 

[v-huizhn-msft]

Hi @cyclist007,

Your colleague can connect your SSAS and create a report without using your .pbix, which works fine? If he can use your SSAS resource data and create new report successfully. It should be caused by the IT during sharing.

Best Regards,
Angelia

[cyclist007]

Thank you @v-huizhn-msft

We did not ask him to try create a report using SSAS, but he could open Power Bi desktop otherwise. 

Anyways as I indicated we found the issue was the read only access needs to be given for each entity in SSAS (including cube).