# Reporting - Dynamic Historical Tags **URL:** \ **Category:** Ignition\ **Tags:** ignition79, scripting, database\ **Created:** [June 13, 2018, 12:40am UTC](https://forum.inductiveautomation.com/t/reporting-dynamic-historical-tags/18435 "2018-06-13T00:40:36Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [June 13, 2018, 3:13pm UTC](https://forum.inductiveautomation.com/t/reporting-dynamic-historical-tags/18435/3 "2018-06-13T15:13:20Z")
> [@paul-griffith](#): > > (even a nested one) See this topic for ideas: > [@Report with Scripted Nested Data](http://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/reporting-dynamic-historical-tags/18435)._