# Report issues with JSON data **URL:** \ **Category:** Ignition\ **Created:** [August 7, 2020, 1:26pm UTC](https://forum.inductiveautomation.com/t/report-issues-with-json-data/37500 "2020-08-07T13:26:46Z")\ **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:** [August 7, 2020, 1:31pm UTC](https://forum.inductiveautomation.com/t/report-issues-with-json-data/37500/2 "2020-08-07T13:31:10Z")
The report generator likes datasets. Consider iterating through your JSON to produce a flat dataset. Or script nested datasets like so: > [@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… (Draw from your JSON instead of scripted queries like that example.) --- _[View the full topic](https://forum.inductiveautomation.com/t/report-issues-with-json-data/37500)._