Pain Point Working with nominal-multi (flattened) tables and banners is a major pain point in Displayr today. A user raised five specific issues, each benchmarked directly against how Walr handles the same task, and in every case, Walr's behavior is either automatic or far simpler than Displayr's. Wrong default % — Displayr defaults flattened tables to row % when crossed with a BANNER or another question is added to the columns, so users have to manually switch to column % every time. Walr auto-detects the table structure and defaults to the correct %. Can't quickly add nets to a row span — In Displayr, this isn't possible without a workaround (see Add nets to each span of a flattened question for the QScript workaround we currently point customers to). In Walr, she can do this quickly by netting up the underlying values directly. Can't add averages to each row span — Not possible in Displayr today, even with a workaround. Possible in Walr: a scaling factor lets users change the values that feed into the averages, and once they do, averages are automatically added to each row span. No automatic sample size per row span — In Displayr, this needs a custom rule to be built. In Walr, it's automatic, including when base sizes differ across spans. Row span labels display poorly — In Displayr, row span labels appear as merged cells running down the side of the table, which is hard to read. In Walr, each span gets its own labeled row at the top of the span, which reads much more clearly. Feature Request Bring flattened nominal-multi table and banner handling up to parity with Walr on the five points above: Auto-detect flattened table structure and default to the correct % (column, not row) without requiring a manual switch. Support adding nets to a row span directly, without the QScript workaround. Support adding averages to a row span, via a scaling factor (or equivalent) applied to the underlying values, with averages generated automatically once applied. Automatically calculate and display sample size per row span, including when base sizes differ across spans, without requiring a custom rule. Redesign row span labels to appear as their own labeled row at the top of each span, rather than as a merged cell running down the side of the table. Why It Matters Flattened nominal-multi tables are a core, frequently-used table type, and right now nearly every step of working with them in Displayr requires a manual fix, a workaround, or isn't possible at all, while a competitor handles all five natively. This is a significant point of friction (and a competitive gap) for a common workflow.