Forum Discussion
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.\r\nParameter name: source
Through testing, we were able to isolate the parameters in which this error occurs: when the paginated report is using a Direct Lake semantic model. We have no issue embedding Power BI reports and/or Power BI reports with paginated report visuals (when the paginated reports aren't using Direct Lake models). Up until 10/25, we had no issues with any embedding (including the paginated reports tied to a Direct Lake model). Since 10/25, we have ran into this issue and have no resolution. Was there an update somewhere that would have caused this embed process to break and what would a resolution be?
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."
7 Replies
- parkergeis
Helper II
For reference, this is the payload that is sent to fetch the embed token. This returns the "Value cannot be null..." error.
{ "reports": [ { "id": "Power_BI_Report_ID" } , {"id": "Paginated_Report_ID"} ], "datasets": [ { "id": "Direct_Lake_Model_ID", "xmlaPermissions": "ReadOnly" } ], "identities": [ { "username": "EMAIL", "roles": ["ROLE"], "datasets": ["Direct_Lake_Model_ID"] } ] } - V-yubandi-msft
Community Support
Hi parkergeis ,
Thank you for engaging with the Microsoft Fabric Community. The Power BI service is currently healthy across all regions, but the Fabric service (which powers Direct Lake models) is showing active advisories globally, as per the Fabric Service Status page.
FYI:Since your paginated reports are connected to a Direct Lake semantic model, the issue may be related to this ongoing Fabric service incident.
We recommend monitoring the Fabric status page for updates. Once the advisory clears, please try embedding again and see if the issue persists.
Microsoft Fabric service status— Community Support Team.
- V-yubandi-msft
Community Support
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
Helper II
Fabric service is now showing good, but the error still persists. This is not a solution.
- V-yubandi-msft
Community Support
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 theValue 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.