Table Chart: Conditional formatting does not apply to Total row and lacks support for string fields

[htcnokia]

Table Chart: Conditional formatting does not apply to Total row and lacks support for string fields

Environment

• Apache Superset Version: 6.1.0
• Chart Type: Table (Pivot Table / Standard Table)

Summary

There are two functional limitations/issues regarding Conditional Formatting in the Table chart visualizer in Superset 6.1.0:

1. Total row ignored: Conditional formatting rules configured for a metric/column are not applied to the generated "Total" or "Subtotal" rows.
2. No support for string/text fields: The Conditional Formatting configuration panel only supports numeric fields and cannot be configured for text/string dimension columns.

---

Issue Details & Steps to Reproduce

Problem 1: Conditional formatting not applied to Total row

1. Create a Table chart with metric columns.
2. Enable the Show Total option under Chart Options.
3. Configure a Conditional Formatting rule for a specific metric (e.g., cell color turns red if value < 0).
4. Observed Result: The rule correctly formats standard data rows, but the Total row remains unformatted (default styling).
5. Expected Result: Conditional formatting rules should evaluate and apply to the aggregated values in the Total / Subtotal row.

Problem 2: Lack of support for text/string dimensions

1. Create a Table chart containing text/string columns (e.g., Status, Category, Region).
2. Open the Conditional Formatting setup drawer/modal.
3. Attempt to select a text/string column to set up string-based rules (e.g., highlight if text equals 'FAILED' or 'CRITICAL').
4. Observed Result: String/text columns are either unavailable in the column selector dropdown or lack comparison operators suited for text evaluation (e.g., Equal to, Contains).
5. Expected Result: Users should be able to apply conditional formatting to string columns based on string conditions (e.g., exact match, contains, regex, or status mapping).

---

Impact

• Total Row Issue: Prevents users from quickly spotting critical high-level aggregated metrics in summary tables.
• String Field Issue: Restricts status-driven visualization (e.g., coloring rows/cells based on workflow states like SUCCESS, PENDING, FAILED).

[dosubot[bot]]

@htcnokia, both of these are genuine gaps in the current Table chart conditional formatting. Here's what the code shows:

1. Conditional formatting not applied to the Total/Summary row

The Footer cell renderer in TableChart.tsx renders totals as plain <strong>{formatColumnValue(column, totals[key])[1]}</strong> with only sharedStyle applied [1]. The columnColorFormatters evaluation that applies conditional formatting backgrounds happens inside the Cell renderer [2], but that path is never invoked for the footer. So the total row simply has no conditional formatting logic at all.

There is an open PR #32425 that adds a "Column Coloring" feature for pivot tables with an optional "Apply color to headers & total rows" checkbox [3], but that is specifically for the Pivot Table and uses fixed column colors rather than rule-based conditional formatting.

2. Only numeric columns are available for conditional formatting

The hasColumnColorFormatters check in TableChart.tsx explicitly requires isNumeric to be true before evaluating any color formatters [4]. The FormattingPopoverContent.tsx operators are all numeric comparisons (>, <, ≥, ≤, =, ≠, between variants), and the target value inputs use InputNumber — there are no text-specific operators like "contains" or "starts with" [5].

Recent related improvements

There have been two merged PRs that expand conditional formatting capabilities, though neither addresses your specific requests:

• PR #34762 added toAllRow (apply formatting to the entire row) and toTextColor (apply formatting as text color instead of background) flags [6].
• PR #35897 added columnFormatting (choose which column to format based on another column's value) and objectFormatting with modes like BACKGROUND_COLOR, TEXT_COLOR, and CELL_BAR [7].

Neither of these adds total-row formatting or string-column support.

What would need to change

• Total row: The Footer cell renderer would need to evaluate columnColorFormatters against totals[key] the same way the Cell renderer does and apply the resulting backgroundColor to the footer <td>. This would be a relatively contained change.
• String support: The column filter would need to include GenericDataType.String columns, and FormattingPopoverContent.tsx would need string-specific operators (Equal, Contains, Starts With, etc.) with a text <Input> instead of <InputNumber>. This is a larger change spanning the control panel and the formatting popover.

Both of these would be new feature/enhancement requests — consider opening separate GitHub issues for each to make them easier to track and contribute to.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.