Forum Discussion
Deneb visual exports blank to PowerPoint while standard Power BI visual exports correctly
We sometimes encounter transient issues with custom visuals that are beyond our control (as their developers). However, I have tested all three export channels on several of my reports, and they all seem to work as expected. Deneb is designed to follow the rendering events that MS requires to signal that it has finished in these scenarios, and they should be exported.
As such, the issue you're seeing might be an issue that hasn't reached my tenant yet (and possibly affects all custom visuals), or an issue with Deneb specifically. And because Deneb is a flexible visual rather than one with a defined use case and a deterministic output, it's often hard to pinpoint issues without specifics about your data or specifications.
To attempt a quick diagnosis: assuming you're using the AppSource version of Deneb (which is the only edition approved for export from reports), if you're using the override row limit feature, MS has indicated to me that anything outside the initial window may not render correctly during export, as it is not the intended use of the feature. Going forward, any visuals that cannot render their data within a single initial window may not be guaranteed to render successfully. I have made my case for this with Deneb, and it has been refused, so in the next release, I will be extending the initial window to the maximum (10K > 30K) to try to mitigate for users, but the doc from the next version will explicitly state that this is no longer possible to support from my side for export and users will have to keep the row count <= 30K if they want visuals to export as expected.
If this doesn't apply, it may be possible that if you are applying dynamic updates to the output after Deneb reports rendering complete (first render). Anything drawn after this will be missed, and it is a feature of the export process and of how we have to signal to MS that a visual is ready. If you're attempting this, you may need to sacrifice these behaviors in favor of stable output/export.
If none of these apply, I'd suggest creating an issue in Deneb's repo with as much detail as possible. Ideally, this should be a report (with shareable data) and your spec so that I can attempt to replicate and isolate as quickly as possible. I provide product development and support in my free time and for free, so anything that can help me solve as simple/fast as possible is going to get to the root of the problem (and fix your issue if I can) will help a great deal.
Many thanks,
Daniel
4 Replies
This looks more like a limitation of how Power BI exports custom visuals than an issue with your report. Since native visuals export correctly and Deneb visuals are blank across all export methods, I'd test with the latest Deneb version and a very simple Vega-Lite visual to confirm. If it still happens, I'd raise it as a Deneb issue (with your PBIX, Deneb version, and Power BI version) because it may be a known limitation of the export rendering pipeline.
We sometimes encounter transient issues with custom visuals that are beyond our control (as their developers). However, I have tested all three export channels on several of my reports, and they all seem to work as expected. Deneb is designed to follow the rendering events that MS requires to signal that it has finished in these scenarios, and they should be exported.
As such, the issue you're seeing might be an issue that hasn't reached my tenant yet (and possibly affects all custom visuals), or an issue with Deneb specifically. And because Deneb is a flexible visual rather than one with a defined use case and a deterministic output, it's often hard to pinpoint issues without specifics about your data or specifications.
To attempt a quick diagnosis: assuming you're using the AppSource version of Deneb (which is the only edition approved for export from reports), if you're using the override row limit feature, MS has indicated to me that anything outside the initial window may not render correctly during export, as it is not the intended use of the feature. Going forward, any visuals that cannot render their data within a single initial window may not be guaranteed to render successfully. I have made my case for this with Deneb, and it has been refused, so in the next release, I will be extending the initial window to the maximum (10K > 30K) to try to mitigate for users, but the doc from the next version will explicitly state that this is no longer possible to support from my side for export and users will have to keep the row count <= 30K if they want visuals to export as expected.
If this doesn't apply, it may be possible that if you are applying dynamic updates to the output after Deneb reports rendering complete (first render). Anything drawn after this will be missed, and it is a feature of the export process and of how we have to signal to MS that a visual is ready. If you're attempting this, you may need to sacrifice these behaviors in favor of stable output/export.
If none of these apply, I'd suggest creating an issue in Deneb's repo with as much detail as possible. Ideally, this should be a report (with shareable data) and your spec so that I can attempt to replicate and isolate as quickly as possible. I provide product development and support in my free time and for free, so anything that can help me solve as simple/fast as possible is going to get to the root of the problem (and fix your issue if I can) will help a great deal.
Many thanks,
Daniel
Hi Olav_Lie
We would like to inquire whether have you got the chance to check the solutions provided by
dm-p carter_gray705 in commiunity to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
Thank you.Hi Olav_Lie
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Thank you.
