cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
dennisnxl
Regular Visitor

Paginated Reports in App - Could not connect to the data source

Hi

I have a paginated report which is built in Power BI Report Builder and it uses shared Power BI dataset with RLS (Premium workspace).

I published the report as an app and I can use it without any problems, but oher users (e.g. external) with access to the App get the following error:

Could not connect to the data source.
There was an error communicating with Analysis Services. Please verify that the data source is available and your credentials are correct. The connection either timed out or was lost.

 

error.JPG

 

I already gave app users Build permission on the dataset as suggested at  Error when accessing paginated reports published to an app - "Could not connect to data source" 
 
Any ideas how to fix that?
 
Btw. I don't want to add all users to the workspace - just to the app.
 
Edit: The report works without RLS, so as workaround I will build the security around separate datasets.
1 ACCEPTED SOLUTION

In this case I simply removed row level security and created a separate dataset for each "role".

Back then it was a classic workspace, but since the new workspace experience is available (which gives more control over roles) it is no longer an issue.

 

More information about differences between classic and new:

https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-upgrade-workspaces

View solution in original post

4 REPLIES 4
Anonymous
Not applicable

Any luck in solving this issue? Have you find a resolution already?

 

BR Frank

In this case I simply removed row level security and created a separate dataset for each "role".

Back then it was a classic workspace, but since the new workspace experience is available (which gives more control over roles) it is no longer an issue.

 

More information about differences between classic and new:

https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-upgrade-workspaces

Anonymous
Not applicable

Hi @dennisnxl,

 

Thank you for your response.

 

Yesterday I did some further testing and I discovered that in our current situation it was caused due to the combination of having an group assignment at role level ("Security") and an individual assignment at permission level ("Manage permissions") regarding the given dataset. It is still under investigation; it might result into a ticket to Microsoft.

 

BR Frank 

Icey
Community Support
Community Support

Hi @dennisnxl ,

Is your data source "Analysis Service"? If it is, do you map user names? If not, please refer to this document to map user names.

 

Best Regards,

Icey

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
June 2022 update 768X460.jpg

Check it out!

Click here to read more about the June 2022 updates!

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Power BI Dev Camp Session 23 768x460.jpg

Check it Out!

Mark your calendars and join us on Thursday, June 30 at 11a PDT for a great session with Ted Pattison!

June 20 episode 7 with aka link 768x460.jpg

The Power BI Community Show

Join us on June 20 at 11 am PDT when Kim Manis shares the latest on Azure Synapse analytics, the Microsoft Intelligent Data Platform, and notable Power BI Updates from Microsoft Build 2022.

Top Solution Authors