# Report Best Way To Display Script Data

**URL:** <https://forum.inductiveautomation.com/t/report-best-way-to-display-script-data/80805>\
**Category:** Ignition\
**Tags:** ignition81, scripting\
**Created:** [October 21, 2023, 5:03pm UTC](https://forum.inductiveautomation.com/t/report-best-way-to-display-script-data/80805 "2023-10-21T17:03:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [October 21, 2023, 5:18pm UTC](https://forum.inductiveautomation.com/t/report-best-way-to-display-script-data/80805/2 "2023-10-21T17:18:26Z")

</div>

You will want to reprocess into a properly nested structure to drive a table group. See this old topic for inspiration:

> [@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/report-best-way-to-display-script-data/80805)._