# Report with Scripted Nested Data

**URL:** <https://forum.inductiveautomation.com/t/report-with-scripted-nested-data/11801>\
**Category:** Ignition\
**Created:** [June 10, 2016, 4:39pm UTC](https://forum.inductiveautomation.com/t/report-with-scripted-nested-data/11801 "2016-06-10T16:39:31Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**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:** [September 29, 2017, 2:35pm UTC](https://forum.inductiveautomation.com/t/report-with-scripted-nested-data/11801/7 "2017-09-29T14:35:32Z")

</div>

Hey Kathy,  
The problem with importing across classloaders could be mitigated by placing the following in the Java class that gets loaded to [system.report](https://docs.inductiveautomation.com/display/DOC79/system.report):

```auto
public static final Class<?> QueryResults = com.inductiveautomation.reporting.common.api.QueryResults.class;

```

Then anyone’s scripts could do:

```auto
from system.report import QueryResults

```

Pretty please?

---

_[View the full topic](https://forum.inductiveautomation.com/t/report-with-scripted-nested-data/11801)._