Forum Discussion
Power BI Subscription Error
Hi All,
We have been receiving an error when trying to send subscriptions for our reports out that contain PDF’s, which is most of what we do. We’ve removed this so we can still push reports, but it’s critical that we have the capability to send PDF’s as attachment in our reports. Is there currently an outage causing this, and if not, can this please be looked into?
Thanks in advance!
10 Replies
Looks like you are still holding on to the legacy Premium workspaces? Any particular reason?
Hi, Anonymous
Based on the information you have provided, I also found a Report in my workspace and downloaded it as a PDF.
The error shown above the image means that your Power BI subscription includes a full report attachment, but your subscription does not support this feature. You can migrate the report to Premium Gen2 or PPU Workspace. You can check this document to get more understanding: Updates to full report attachments for email subscriptions in Premium Gen2 | Microsoft Power BI Blog | Microsoft Power BI
If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .
How to Get Your Question Answered Quickly
Best Regards
Yilong Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello,
Please view my response in this thread: PDF Export not Exporting - Microsoft Fabric Community
Thank you
Hello All,
I did received the report with the PDF attached which was scheduled by others,
however, I just tried sending one myself and am still receiving the error. The same error is still being seen by my other team member as well, so it is still existing on our end when trying to send the PDF attachment.
Thanks in advance!
From the response in the thread linked above, the bug is that you cannot use the "Send Now" button if the subscription is disabled and the full report attachment is set. The subscription needs to be in an enabled state until the fix has fully rolled out. In order to get it an enabled state you will need to follow the steps I left in the above thread as well.
Feel free to respond if you have any other issues with this specific problem.
