Power BI Reports Integration with Azure DevOps - Seeking Clarification

[nush]

Hello everyone,

I'm currently conducting a feasibility study on integrating our Power BI reports with GIT (Azure DevOps). So far, I’ve set up two environment workspaces: Staging and Production. The Staging branch in Azure DevOps has been integrated with the Staging workspace, and I’ve created a deployment pipeline to promote changes from the Staging workspace to Production. I've managed to successfully deploy the full lifecycle of a report, but I have a few questions that need clarification:

1. File Size Limit: According to the Microsoft Learning site, the maximum file size for a report is 25MB. However, I was able to add a report with a file size of 48MB to my Staging workspace by committing the code to the repository. The document was last updated on July 24. Has the file size limit changed recently? Will this pose a problem in the future, especially with larger reports as I have quite a few of them?

2. .pbix File Download: The same article mentioned that .pbix files cannot be downloaded from the service after they have been deployed using GIT integration. However, I was able to download the .pbix file. Am I missing something, or does the documentation need an update?

3. Publishing .pbip Files: I’ve read (though I can’t recall the source) that if we convert a .pbix file to a .pbip (project) file, the "Publish" feature on the report will be greyed out. However, I was able to publish my .pbip file to the Staging workspace directly, without committing it to the GIT repository. Is there a way to disable this direct report publishing feature?

4. Bug Fix in Production when using deployment pipeline: After making feature changes to an existing report, I committed the changes to the Staging branch and refreshed the Staging workspace. While the feature testing is still in progress ( haven't deployed it to the production yet), a bug was reported in the report in the Production workspace. As there's no concept of main branch in the deployment pipeline concept, how can I address the bug in Production while my Staging repo already contains feature changes?

I realize these are quite a few questions, but I’d greatly appreciate any insights or assistance.

Thank you!

[nush]

@v-zhangtin-msft 

Hi Charlotte,

Thanks for your reply.  What I was trying to say is the microsoft document is not correct or upto date re the first 3 points I discussed above. 

I would really like to get ideas regarding my 4th point as well.

Thank you

[v-zhangtin-msft]

Hi, @nush 

For more information on file size limits and submitting more files, you can refer to:

https://learn.microsoft.com/en-us/fabric/cicd/troubleshoot-cicd#maximum-commit-size-exceeded 

If you were able to download the .pbix file, there might be specific conditions under which the download is allowed. It is recommended to keep an eye on the official documents for updates.

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.