Forum Discussion

benbellavaap's avatar
benbellavaap
Frequent Visitor
1 year ago
Solved

Power BI Embedded - Paginated Report Visual

I'm seeking support troubleshooting a paginated report visual error received through Power BI embedded analytics using the embed for customers or app owns data method.  Below, I've pasted the visual error message I'm encountering when trying to populate the report in the Power BI Embedded Analytics Playground.  In the Playground, I input the embed token, embed url, and tenant id.  Other visuals on the same page such as a clustered bar chart and mult-row card do render successfully, but not the paginated report visual.  I've read the paginated report visual considerations and limitations section in MSFT learn, which led me to the embed for customers method.  There is no row-level security or object level security applied and the intended audience is the general public.  I would simply use publish to web functionality, but the limitation suggested i needed to go with app owns data.  I've setup a service principal and client secret to authenticate.  The service principal has microsoft graph user.read and power bi service report.read.all api permissions granted for the tenant.  In the Power BI service, I believe i've extended all the necessary tenant setting & workspace permissions to the service principal too.  The paginated report is being sourced from the same semantic model as the report featuring the paginated report visual.  All artifacts are contained in the same workspace which is assigned an F8 capacity.  

 

I welcome any advice on how to troubleshoot.  

 

An unexpected error occurred

Timestamp: 2025-02-28T15:51:12.422Z
Root activity ID: 1bae75ba-ff90-4a99-ab36-59bb0062204f
Session ID:
Tenant ID: undefined
Cluster: https://WABI-US-CENTRAL-B-PRIMARY-redirect.analysis.windows.net
Report ID:
Capacity ID: undefined
ReportViewerVersion: undefined

13 Replies

  • v-saisrao-msft's avatar
    v-saisrao-msft
    Community Support

    Hi benbellavaap,

    Thank you for reaching out to the Microsoft Fabric community.

     

    I understand that you are attempting to embed a Power BI report featuring a Paginated Report Visual using Power BI Embedded but are facing an issue where the Paginated Report Visual fails to render, although other visuals are displaying correctly. 

    Unfortunately, embedding a Power BI report that includes a Paginated Report Visual using Power BI Embedded is not supported. This limitation is documented in Microsoft’s official documentation: 
    Create and use the paginated report visual - Power BI | Microsoft Learn 

    • Utilize the Paginated Report Embedding API to directly embed the paginated report, rather than embedding it within a Power BI report. 

             For Reference use the below link: 

             Embed a paginated report - Power BI | Microsoft Learn 

    • Please ensure that the embed token includes the Report.Read.All permission, as it is necessary for reading paginated reports. 
    • When generating the embed token, please retrieve the Paginated Report’s embed URL from the Power BI REST API response instead of using the Power BI report’s embed URL. 

    If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

     

    Thank you. 

  • benbellavaap's avatar
    benbellavaap
    Frequent Visitor

    I very much appreciate your response.  However, I do not have a shared understanding that the paginated report visual is not supported.  I'm familiar with the considerations and limitations of the paginated report visual.  Specifically, "When embedding a Power BI report that contains a paginated report visual, using the embed for your customers method, you need a service principal and a multi-resource embed token as explained in How to embed a Power BI report that contains a paginated report visual."

    This suggests it is possible to embed a paginated report visual, if following the embed for customers method.  I've been following such steps, but am still encountering an issue.  

    Are you suggesting the microsoft learn documentation is misleading and needs to be revised?

    Thanks,
    Ben

  • benbellavaap's avatar
    benbellavaap
    Frequent Visitor

    I made some adjustments to my GenerateToken Power BI REST API call and now I'm receiving a slightly different error message.  In the Power BI Embedded Analytics Playground, the paginated report visual initially attempts to render reading "Loading Report", but then fails.  Here is the link MSFT learn documentation I'm referencing as an example for the Generate Token call.

    Unable to render paginated report
    Connection open intermittent error while reading in Analysis Services, needs retry.
    Timestamp: 2025-03-04T01:45:02.227Z
    Root activity ID: 22318aac-7b4f-4f64-bf82-aa679c40e44e
    Session ID: 000019bcdb074aa5b9af7b416ddea224
    Tenant ID: undefined
    Cluster: https://WABI-US-CENTRAL-B-PRIMARY-redirect.analysis.windows.net
    Report ID: 2a5170e4-0400-42f3-b655-19b07731e9b1
    Capacity ID: undefined
    ReportViewerVersion: undefined

  • benbellavaap's avatar
    benbellavaap
    Frequent Visitor

    In troubleshooting, I've achieved success embedding a paginated report visual where the data was manually entered into the .rdl file.  My intent is to source the paginated report data from a Power BI semantic model, instead.  The other variable in this successful test compared to the error I'm receiving in the report I'm aiming to embed was the creation of the .rdl in Power BI Report Builder desktop app vs. the web authoring in the Power BI service.  

  • benbellavaap's avatar
    benbellavaap
    Frequent Visitor

    Some additional steps I've taken to troubleshoot:

    - granted the service principal additional API permissions including: capacity.read.all, dataset.readwrite.all, paginatedreport.readwrite.all, report.readwrite.all, semanticmodel.readwrite.all, tenant.read.all

    - confirmed my Fabric tenant setting allows xmla endpoints and the fabric capacity xmla endpoint is set to read write (among other service principal related tenant setting allowances)

    - security group the service principal is apart is an 'Admin' for the workspace in question, as well as assigned the Fabric Administrator role

  • benbellavaap's avatar
    benbellavaap
    Frequent Visitor

    Here is the GenerateToken call script and latest paginated report visual error message i'm encountering...

    curl --location 'https://api.powerbi.com/v1.0/myorg/GenerateToken' \
    --header 'Content-Type: application/json' \
    --header 'Authorization: Bearer {{value}}' \
    --data '{
    "datasets": [
    {
    "id": "{{dateset_id}}",
    "XmlaPermissions": "ReadOnly"
    }
    ],
    "reports": [
    {
    "allowEdit": false,
    "id": "{{report_id}}"
    },
    {
    "id": "{{paginated_report_id}}"
    }
    ]
    }'

    Unable to render paginated report
    Connection open intermittent error while reading in Analysis Services, needs retry.
    Timestamp: 2025-03-06T03:55:57.041Z
    Root activity ID: 9b596914-7877-4457-9328-a1f1242c7e63
    Session ID: 00001ce0028841a59070fa897c99e73e
    Tenant ID: undefined
    Cluster: https://WABI-US-CENTRAL-B-PRIMARY-redirect.analysis.windows.net
    Report ID: 2a5170e4-0400-42f3-b655-19b07731e9b1
    Capacity ID: undefined
    ReportViewerVersion: undefined

    • v-saisrao-msft's avatar
      v-saisrao-msft
      Community Support

      Hi benbellavaap,

      Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

       

      Thank you for your understanding and assistance.

      • benbellavaap's avatar
        benbellavaap
        Frequent Visitor

        Yes, I'll be happy to share the outcome of the MSFT support ticket, once a solution is identified.

  • v-saisrao-msft's avatar
    v-saisrao-msft
    Community Support

    Hi benbellavaap,
    Could you please confirm if the issue was resolved after raising a support case? If so, we’d appreciate it if you could share the solution to help others in the community. As we haven’t heard back, we’re closing this thread. For any further issues, please raise a new thread in the Microsoft Fabric Community Forum — we’ll be happy to assist.

    Thank you for being part of the Microsoft Fabric Community.

    • benbellavaap's avatar
      benbellavaap
      Frequent Visitor

      After numerous engagements with MSFT support over many weeks, we were unable to render paginated report visuals when embedding the Power BI report involving a paginated report sourcing from a semantic model.  Due to time limitations, I had to resort to sourcing the paginated report directly from the source (Snowflake database), which was successful.  This was frustrating though since it required additional work and it's not as performant from both a time to render & compute usage perspective.