# Ignition – Report Module – How to set dynamic the Data Key in a Timeseries chart **URL:** \ **Category:** Ignition\ **Tags:** reporting\ **Created:** [May 8, 2025, 9:38am UTC](https://forum.inductiveautomation.com/t/ignition-report-module-how-to-set-dynamic-the-data-key-in-a-timeseries-chart/106028 "2025-05-08T09:38:17Z")\ **Posts on this page:** 1\ **Showing post:** 10
**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 9, 2025, 11:07am UTC](https://forum.inductiveautomation.com/t/ignition-report-module-how-to-set-dynamic-the-data-key-in-a-timeseries-chart/106028/10 "2025-05-09T11:07:33Z")
Report preview in the designer shows the data in XML format in the right sidebar. If you are trying to produce **nested** data by **script** , you need to see this old topic: > [@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/ignition-report-module-how-to-set-dynamic-the-data-key-in-a-timeseries-chart/106028)._