Merging/Grouping of key values in table chart

[tmottura-interfacing]

Is there any way to have key values grouped or merged in a table where you have hierarchy ?
It seems you are compelled to accept that key values are repeated if there are several elements belonging to it.
Many thanks.

[dosubot[bot]]

Hi @tmottura-interfacing! I'm Dosu and I’m helping the superset team.

Cell merging in Superset table charts is not currently supported — it's a feature that has been requested but isn't available yet.

Superset does have row grouping for table charts, but this groups data logically without visually merging the repeated parent values you're trying to avoid.

Workaround: You can use the "Render Columns in HTML Format" option with custom SQL expressions containing HTML/CSS to create visual grouping effects. This isn't true cell merging, but it can help approximate a hierarchical display by styling cells differently based on your data structure.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[aniruddhaadak80]

To merge or group key values natively in a Superset Table Chart, you should use the 'Pivot Table v2' visualization instead of the standard Table. It allows you to drag dimensions to rows/columns and handles hierarchical grouping and subtotals out-of-the-box.

[fowlerp397-tech]

Appreciate you opening this issue

…

On Sat, Mar 14, 2026, 12:58 AM ANIRUDDHA ADAK ***@***.***> wrote: Hello @tmottura-interfacing <https://github.com/tmottura-interfacing>, Thanks for opening this up! Usually, with these kinds of underlying issues, the first step is double-checking if there is a minor version mismatch in your installed environment tooling vs the actual framework requirements. Have you tried outright clearing the respective local build/cache directories, forcing a clean slate reinstall, and ruling out any implicit breaking changes from recent patches? If you are still hitting the exact same bottleneck, dropping a minimal reproduction steps (or specifically the raw error logs) here usually gets it sorted out way faster by the maintainers. Hope this helps point you in the right direction. Let me know if you make any progress! — Reply to this email directly, view it on GitHub <#38640 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B72HASLN5JPODANKPCOVUID4QTYIJAVCNFSM6AAAAACWRNC73OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMJSG43TSOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>