# Error Report Viewer, using nested Query

**URL:** <https://forum.inductiveautomation.com/t/error-report-viewer-using-nested-query/83090>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [December 13, 2023, 3:19pm UTC](https://forum.inductiveautomation.com/t/error-report-viewer-using-nested-query/83090 "2023-12-13T15:19:15Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [December 13, 2023, 4:32pm UTC](https://forum.inductiveautomation.com/t/error-report-viewer-using-nested-query/83090/8 "2023-12-13T16:32:44Z")

</div>

avec ca:

> [@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…

et un `itertools.groupby`.

Mais te lances pas là dedans tout de suite, attends un peu d'avoir d'autres avis.

---

_[View the full topic](https://forum.inductiveautomation.com/t/error-report-viewer-using-nested-query/83090)._
