Products | Versions |
---|---|
Spotfire Analyst | All |
This issue originates from custom code (Note: This is not a product issue.) calling the context.signalRenderComplete() API too early, before the visualization has fully rendered. Spotfire relies on this signal to determine when the visualization is ready for export or capture.
If this signal is sent too early—especially when the visualization has not yet received necessary data (for example, lacking values on the x-axis)—the export process will capture a blank or incomplete visual.
An additional contributing factor can be the Spotfire Mod employing multiple readers with independent callback functions, each attempting to render the visualization separately. This can lead to inconsistent rendering behavior and premature signaling of completion.
To reliably ensure your custom Spotfire Mod visualizations appear in PDF exports, implement the following strategies:
By ensuring that the rendering process is complete before signaling, PDF exports and previews will consistently capture the accurate visual state.
In some instances, custom Spotfire Mods visualizations do not appear in exported PDF files or during export previews within Spotfire. This behavior can be intermittent and may affect custom Spotfire Mods based on their implementation.
Doc: Knowing what changed
Community: Developer Hub for Spotfire Mods - Fundamentals