Forum Discussion

mp390988's avatar
mp390988
Icon for Post Partisan rankPost Partisan
1 year ago
Solved

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 gi...
  • rajendraongole1's avatar
    1 year ago

    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.

     

     

  • sivarajan21's avatar
    1 year ago

    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.

      OptionHow to ImplementTrade-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,