# Report - Nested Queries - Accessing variables thru scripting **URL:** \ **Category:** Ignition\ **Tags:** reporting\ **Created:** [January 31, 2024, 2:42pm UTC](https://forum.inductiveautomation.com/t/report-nested-queries-accessing-variables-thru-scripting/85014 "2024-01-31T14:42:43Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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 31, 2024, 2:56pm UTC](https://forum.inductiveautomation.com/t/report-nested-queries-accessing-variables-thru-scripting/85014/2 "2024-01-31T14:56:40Z")
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/report-nested-queries-accessing-variables-thru-scripting/85014)._