Forum Discussion

parkergeis's avatar
parkergeis
Icon for Helper II rankHelper II
10 months ago
Solved

Embedding Power BI Reports with Paginated Reports (Direct Lake model)

We have Power BI reports with paginated report visuals that are experiencing the below error in our embedded environment:   errorType: "INVALID" fieldErrors: null message: "Value cannot be null.\...
Need Help
  • parkergeis's avatar
    parkergeis
    10 months ago

    Microsoft support got back with me after internal discussions with the product team.

     

    "Engineering team identified a recent regression in the Embedtoken generation for Paginated Reports connected to DirectLake datasets. This issue, caused by a null reference exception due to a newly added validation, has been identified and a fix has already been checked in. The fix is expected to be deployed to production on November 21st or 22nd, 2025. As a workaround, you can resolve the issue by passing "datasourceIdentities": [] in the token generation request, which will have no impact on the functionality."

     

V-yubandi-msft's avatar
V-yubandi-msft
Icon for Community Support rankCommunity Support
10 months ago

Hi parkergeis ,
May I know if your issue has been resolved, or do you still need any additional details. Please let us know if you require any further information.

 

Thank You.

parkergeis's avatar
parkergeis
Icon for Helper II rankHelper II
10 months ago

Fabric service is now showing good, but the error still persists. This is not a solution.

  • V-yubandi-msft's avatar
    V-yubandi-msft
    Icon for Community Support rankCommunity Support
    10 months ago

    Hi parkergeis ,
    Thanks for the update. Since this was working fine before Oct 25, it looks like a backend change on the Microsoft side affected how Paginated Reports connect to Direct Lake when they’re embedded. Because of that change, the report is now showing the

    Value cannot be null (source)

    As an alternate, Open the paginated report in Report Builder and switch the data source from Direct Lake to DirectQuery, then republish. This doesn’t require any changes to your dataset or embed token.

    If staying on Direct Lake is important for your scenario, it would be best to open a support ticket with Microsoft so team will contact you.

    Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

     

    Let me know how you want to proceed your experience may help others running into the same issue.

     

    thank You.

    • V-yubandi-msft's avatar
      V-yubandi-msft
      Icon for Community Support rankCommunity Support
      10 months ago

      Hi parkergeis , just checking in. Did the previous suggestion help resolve the issue, or have you raised a support ticket with Microsoft?
      If you need any additional details or assistance, please let us know.

       

      Thanks.

      • parkergeis's avatar
        parkergeis
        Icon for Helper II rankHelper II
        10 months ago

        Microsoft support got back with me after internal discussions with the product team.

         

        "Engineering team identified a recent regression in the Embedtoken generation for Paginated Reports connected to DirectLake datasets. This issue, caused by a null reference exception due to a newly added validation, has been identified and a fix has already been checked in. The fix is expected to be deployed to production on November 21st or 22nd, 2025. As a workaround, you can resolve the issue by passing "datasourceIdentities": [] in the token generation request, which will have no impact on the functionality."