Skip to main content
Question

Org Chart Formatting Inconsistencies

  • March 31, 2026
  • 1 reply
  • 16 views

Forum|alt.badge.img+2

When building Org Charts, I have observed inconsistencies in formatting. If I format my metrics as Rich Text, and apply bold or italics formatting, it will not show such in Org Chart Tiles, but if I click on a tile and see the same in expanded form, it shows proper formatting.

Similarly, I also want to show ‘0’ as “-”. I applied this using ‘zero display’ formatting setting to ‘-’. It changes so in table view but as soon as we shift to org chart view, it doesn’t show it. Moreover, in table view in gets rid of any prefix applied. Prefix are required when showing any property or value. So, I want that I can change blanks or zeroes to “-” and have prefixes intact within the org chart. Currently I have achieved this using text metrics, but would be better, if I can directly format number metrics for an org chart

Do these inconsistencies stem from limitations within the tool, or is there a more appropriate way to apply the formatting?

1 reply

KeeganSF
Employee
Forum|alt.badge.img+2
  • Employee
  • April 1, 2026

Hi,

Great observations! Thanks for documenting these details.

The formatting differences you're seeing between table view and Org Chart view are known limitations of how the Org Chart currently renders data:

  • Rich Text (bold/italics): Org Chart tiles use a simplified rendering and don't display rich text formatting. The expanded detail panel does show it correctly, but the tile-level display doesn't support it yet.
  • Zero display & prefix/suffix: Number display settings (zero display, prefixes, suffixes) are currently scoped to table/grid views. The Org Chart pulls the raw numeric value and doesn't apply these formatting options.
  • Prefix being stripped when zero display is set in table view: This sounds like unintended behavior — those settings should work independently. I'd recommend raising this through a support ticket so it can be investigated properly.

Your workaround with text metrics is the right approach for now — it's the most reliable way to get consistent formatting across both views. We know it adds modeling effort, and this feedback has been shared with our product team.