# Report : Stop escalation on Nested Queries with field conditional **URL:** \ **Category:** Ignition\ **Created:** [January 17, 2019, 9:30pm UTC](https://forum.inductiveautomation.com/t/report-stop-escalation-on-nested-queries-with-field-conditional/21955 "2019-01-17T21:30:07Z")\ **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 18, 2019, 1:47pm UTC](https://forum.inductiveautomation.com/t/report-stop-escalation-on-nested-queries-with-field-conditional/21955/2 "2019-01-18T13:47:33Z")
Yes, but only via scripting. See this thread for inspiration: > [@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/report-stop-escalation-on-nested-queries-with-field-conditional/21955)._