# Module Report - dynamic chart data key

**URL:** <https://forum.inductiveautomation.com/t/module-report-dynamic-chart-data-key/59163>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 3, 2022, 2:31pm UTC](https://forum.inductiveautomation.com/t/module-report-dynamic-chart-data-key/59163 "2022-05-03T14:31:56Z")\
**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:** [May 3, 2022, 3:05pm UTC](https://forum.inductiveautomation.com/t/module-report-dynamic-chart-data-key/59163/2 "2022-05-03T15:05:51Z")

</div>

I'm pretty sure you are going to need nested data. You can do this in a script if needed:

> [@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/module-report-dynamic-chart-data-key/59163)._