To continue to deliver the best possible experience when working with data visualisations, we've recently upgraded the charting engine that powers many of our views.

This new version brings a range of enhancements, fixes and performance improvements - particularly around styling and layout. While we've taken care to preserve existing appearances wherever possible, you may notice some subtle differences. These are the result of a more modern, responsive rendering approach designed to offer greater consistency and clarity across all view types.

We are confident that this upgrade will provide a more consistent, flexible and future-ready reporting experience. It also paves the way for a series of upcoming enhancements, including new view types such as Tree-graph and Pictograph.

Key improvements

Smarter space usage.

Axis labels now fit more efficiently, reducing unnecessary line breaks and conserving space.

[Screenshot here]

Improved label handling

Labels that were previously truncated (e.g. in Pe views) now wrap intelligently, allowing you to see more complete text.

[Screenshot here]

Refined layouts

Minor adjustments to axis placement and graphical elements (such as bars or lines) improve overall alignment.

[Screenshot here]

Enhanced colour framework

Improvements to contrast handling and colour logic support greater visual accessibility and consistency.

[Screenshot here]

Focused rendering at small sizes

When views are displayed at reduced sizes, the engine prioritises data visibility, even if that means trimming or repositioning secondary elements like axes.

[Screenshot here]

Known issues

Packed bubble labels

In the Packed Bubble view, labels may currently be missing when simulation is disabled. This issue is tracked and a fix is planned.

[Screenshot here]

What do I need to do?

We've tested and tuned views extensively to minimise any disruption, so you should be able to upgrade without noticing any major differences, however given the broad range of configuration options, it's possible some issues may arise.

We strongly recommend testing in a staging environment first with some of your key reports. If you notice anything unusual, please let us know.