# Table Grouping in Reporting Module

**URL:** <https://forum.inductiveautomation.com/t/table-grouping-in-reporting-module/55116>\
**Category:** Ignition\
**Tags:** ignition80, ignition81\
**Created:** [January 18, 2022, 3:50pm UTC](https://forum.inductiveautomation.com/t/table-grouping-in-reporting-module/55116 "2022-01-18T15:50:15Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 18, 2022, 4:29pm UTC](https://forum.inductiveautomation.com/t/table-grouping-in-reporting-module/55116/3 "2022-01-18T16:29:54Z")

</div>

If you want a variable report format, where parts of the report vanish when not needed, you **must** use nested queries. Or, get a nested query structure via script. That is, query efficiently with joins, then reformat into a new data key with nested keys programmatically. See this topic for the basic procedure:

> [@Report with Scripted Nested Data](https://forum.inductiveautomation.com/t/report-with-scripted-nested-data/11801):
>
> The report datasource scripting examples explain how to access the nested data in another key for use constructing a custom dataset. What I don’t see is how to construct nested data that would be suitable for use with a child table in a table group. I have a parent dataset that I’m constructing via script due to annoying limitations of an ancient SQL Server 2000 instance. I need a subquery for each row that could be done with a normal query, but there’s no way to add a regular subquery to a s…

---

_[View the full topic](https://forum.inductiveautomation.com/t/table-grouping-in-reporting-module/55116)._