Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I have a custom python visual in a published report that has recently stopped working. I have confirmed that the visual still works with a local version of python 3.7.7 with all packages aligning to the versions listed here: https://learn.microsoft.com/en-us/power-bi/connect-data/service-python-packages-support.
The visual has been working for roughly 8+ months without a single issue or change and i noticed today (3.17.2025) that it no longer works and i am receiving a error message that does not help me at all "Script Runtime Error --> statement execution failed with status: error". Is anyone else experiencing this or aware of any known issues that could cause this?
Solved! Go to Solution.
@Deku Thank you for the context of the plan to upgrade. I believe it was and the documentation is out of date. Another person on my team was running into the same problem and upgraded from matplotlib 3.2.2 to 3.5.0 on our local version of python (3.7.7) and we could recreate the issues. Turns out that the "b" keyword argument to plt.grid() was deprecated in version 3.5.0 and changed to "visible". Once changed in the custom python visual, the report was no longer experiencing issues.
@Deku Thank you for the context of the plan to upgrade. I believe it was and the documentation is out of date. Another person on my team was running into the same problem and upgraded from matplotlib 3.2.2 to 3.5.0 on our local version of python (3.7.7) and we could recreate the issues. Turns out that the "b" keyword argument to plt.grid() was deprecated in version 3.5.0 and changed to "visible". Once changed in the custom python visual, the report was no longer experiencing issues.
Hi @tuckbrit ,
Thank you for reaching out to the Microsoft Fabric Community. Also @Deku and @lbendlin for your inputs and actively participating in the community forum and for the solutions you’ve been sharing in the community forum.
To resolve your issue with the custom Python visual in Power BI Service, first, ensure that your script only uses Power BI Service-supported Python packages by checking the latest list here.
Next, test whether Python execution works at all in Power BI Service by running a simple script like print("Hello World"). If this fails, the problem may be with Power BI’s execution environment. Additionally, try re-publishing the report from Power BI Desktop after confirming the visual works locally, as this can refresh dependencies and resolve potential conflicts. Also, check if there have been changes to the dataset, such as missing values or new column types, which could cause execution failures.
Since Power BI Service has execution limits on memory and processing time, consider optimizing your script if it processes large datasets. If none of these steps resolve the issue, you may need to open a Microsoft support ticketas mentioned by @lbendlin .
I hope my suggestions give you good idea, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
There was a plan to upgrade python
https://powerbi.microsoft.com/en-us/blog/important-update-coming-to-r-py-visuals-in-power-bi/
Maybe finally happened. Not seen anything about it since that blog post though
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
59 | |
33 | |
27 | |
25 | |
24 |
User | Count |
---|---|
63 | |
53 | |
32 | |
24 | |
20 |