# How does ignition execute queries in report scripting **URL:** \ **Category:** Ignition\ **Tags:** scripting, reporting\ **Created:** [June 27, 2025, 1:39pm UTC](https://forum.inductiveautomation.com/t/how-does-ignition-execute-queries-in-report-scripting/107881 "2025-06-27T13:39:50Z")\ **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:** [June 27, 2025, 1:44pm UTC](https://forum.inductiveautomation.com/t/how-does-ignition-execute-queries-in-report-scripting/107881/2 "2025-06-27T13:44:57Z")
The report won't be generated at all until the script data source runs completely. It will only run once per report request. It will still run even if the report design doesn't use `@QueriedData@`. It won't run again even if you reference `@QueriedData@` multiple times. It seems like you want scripted **nested** data. See this 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/how-does-ignition-execute-queries-in-report-scripting/107881)._