Forum Discussion
parkergeis
Helper II
Helper IIEmbedding 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.\...
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."
parkergeisHelper II
Helper IIFor 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"]
}
]
}