# Report module - change component properties by script **URL:** \ **Category:** Ignition\ **Created:** [January 24, 2020, 8:18am UTC](https://forum.inductiveautomation.com/t/report-module-change-component-properties-by-script/31586 "2020-01-24T08:18:53Z")\ **Posts on this page:** 1\ **Showing post:** 5
**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:** [December 17, 2021, 1:43pm UTC](https://forum.inductiveautomation.com/t/report-module-change-component-properties-by-script/31586/5 "2021-12-17T13:43:01Z")
I've created completely dynamic reports using nested tables to match a set of nested data keys. For the parts of the report that I wanted to omit, I ensured the corresponding nested query returned no rows. Creating a such a nested data key _ **via script** _ is rather complicated, though. 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/report-module-change-component-properties-by-script/31586)._