Forum Discussion
Paginated Report error
Hi,
A paginated report has been created using a power bi model as the data source.
Below is the item lineage for the paginated report.
As you can see, it uses model Z.
The end user has been given read permissions for model Z however they have not been granted access for model X and Y because we don't want them to have access to these models as it contains sensitive data.
Think of model Z as a filtered version of Model Y.
However, when the user tries to open the report, they get the below error message:
Anyone have any idea why this is happening?
Hi mp390988 - Create a standalone dataset specifically for the purpose of filtered access (Model Z) rather than relying on filters on the fly from shared datasets.If Model Z is derived from Model Y (e.g., filtered), consider creating a separate dataset for Model Z and publishing that independently.This way, the report connects only to the filtered dataset with no underlying ties to the sensitive models.
Dataset permissions required for App report in Power BI? What am I missing??? (Re-Upload)
Whole Report does not work, because of missing acc... - Microsoft Fabric Community
Hope the above information works.
Hi mp390988
This error occurs because paginated reports always validate credentials all the way back through the semantic model chain, not just the final model Z.
Even though your report queries only Z, the Power BI service can’t resolve Z without also validating X and Y, because Z is built on top of them.What’s Happening
Lineage: X → Y → Z → Paginated report
The user has read access to Z only.
When the paginated report opens, the Analysis Services engine attempts to connect through the whole chain (Z → Y → X) to resolve metadata.
Since the user lacks permissions on X and Y, the authentication to the underlying models fails and you get
Unable to render paginated report – error communicating with Analysis Services.
Option How to Implement Trade-offs 1. Grant “Build” or “Read” access on upstream models (X and Y) In the Power BI Service → each dataset → Manage Permissions → Add the user with at least Read (or Build if you need to create further models). Easiest to implement but exposes X and Y to the user (even if they never open them). 2. Break the chain (publish Z as a physical dataset) In Power BI Desktop, connect to Z and Import the data or Publish as a separate dataset that does not reference X/Y live. Then point the paginated report directly at this new dataset. Users only need access to the new dataset, but you lose live-through updates unless you schedule refresh. Recommended
If you must keep X and Y hidden:
Deploy Z as its own imported dataset (Option 2)
Please let me know if it works
Best Regards,
5 Replies
Hi mp390988 - Create a standalone dataset specifically for the purpose of filtered access (Model Z) rather than relying on filters on the fly from shared datasets.If Model Z is derived from Model Y (e.g., filtered), consider creating a separate dataset for Model Z and publishing that independently.This way, the report connects only to the filtered dataset with no underlying ties to the sensitive models.
Dataset permissions required for App report in Power BI? What am I missing??? (Re-Upload)
Whole Report does not work, because of missing acc... - Microsoft Fabric Community
Hope the above information works.
Hi mp390988
Thank you for reaching out to the Microsoft Fabric Forum Community.
rajendraongole1 Thanks for the inputs.
I hope the information provided by user was helpful. If you still have questions, please don't hesitate to reach out to the community.
Hi mp390988
This error occurs because paginated reports always validate credentials all the way back through the semantic model chain, not just the final model Z.
Even though your report queries only Z, the Power BI service can’t resolve Z without also validating X and Y, because Z is built on top of them.What’s Happening
Lineage: X → Y → Z → Paginated report
The user has read access to Z only.
When the paginated report opens, the Analysis Services engine attempts to connect through the whole chain (Z → Y → X) to resolve metadata.
Since the user lacks permissions on X and Y, the authentication to the underlying models fails and you get
Unable to render paginated report – error communicating with Analysis Services.
Option How to Implement Trade-offs 1. Grant “Build” or “Read” access on upstream models (X and Y) In the Power BI Service → each dataset → Manage Permissions → Add the user with at least Read (or Build if you need to create further models). Easiest to implement but exposes X and Y to the user (even if they never open them). 2. Break the chain (publish Z as a physical dataset) In Power BI Desktop, connect to Z and Import the data or Publish as a separate dataset that does not reference X/Y live. Then point the paginated report directly at this new dataset. Users only need access to the new dataset, but you lose live-through updates unless you schedule refresh. Recommended
If you must keep X and Y hidden:
Deploy Z as its own imported dataset (Option 2)
Please let me know if it works
Best Regards,
Hi mp390988
I wanted to check if you had the opportunity to review the information provided by users. Please feel free to contact us if you have any further questions.
Hi mp390988
Hope everything’s going smoothly on your end. I wanted to check if the issue got sorted. if you have any other issues please reach community.
