The payload size exceeds limits when deploying Power BI report

[gjoaquim]

Library Version

0.1.8

What is the problem?

I was testing to deploy a semantic model and a report to my workspace. The semantic model worked fine but I get an error when deploying the report:

• ERROR - fabric_cicd._common._fabric_endpoint - Unhandled error occurred calling POST on 'https://api.fabric.microsoft.com//v1/workspaces/XXXXXXXX/items'. Message: The payload size exceeds limits.

I tried deploying the report using the pbir format and also without it.

Is there an ideal solution?

Is it possible to split the payload or is the payload size a limit from Microsoft?

Additional context, screenshots, logs, error output, etc

No response

[JacobKnightley]

By chance could you share the PBI? We haven't ran into this before so likely we're not attempting to deploy such a large report.

[gjoaquim]

Unfortunately I can't share the PBI file. But see the size of the report.json file attached here:

Is there any log that could help you? I am also open for a quick call to show you.

I also tried to deploy the report using the Rui Romano PowerShell code: https://learn.microsoft.com/en-us/rest/api/fabric/articles/get-started/deploy-project

But I also got the same error, see the logs from the error using the deployment with PowerShell (which it also uses the same Fabric REST API endpoint):

logs_error_powershell.txt

[JacobKnightley]

By chance were you able to get this committed to ADO/GitHub? I think the file size exceeds the max allowed. If you were able to commit this using the workspace GIT sync, then we certainly can escalate this. We don't want to have a mismatch between what you can commit and what you can deploy

[gjoaquim]

Yes. I created two versions, one with the pbir format for the report and another without it (legacy format with report.json). I could commit both versions to ADO. I also tried to use the workspace GIT sync and it worked. See the picture below:

[JacobKnightley]

Thank you! I'll see what we can do. We're hitting the max payload size from the public API and there's no way around it. Working with the API team to discuss the mismatch between git sync and public APIs, we should be able to deploy anything that is committed. Although I don't expect this to be a short term fix, so in the meantime I'd recommend you consider downsizing your report a bit if possible

[gjoaquim]

Ok. Thank you. Please keep me informed if you have any news. I also posted this issue today in the Microsoft Enterprise Voice Community Teams channel, hoping to escalate this issue asap.