# Reporting: Dynamic chart timespan

**URL:** <https://forum.inductiveautomation.com/t/reporting-dynamic-chart-timespan/60010>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [May 25, 2022, 2:17pm UTC](https://forum.inductiveautomation.com/t/reporting-dynamic-chart-timespan/60010 "2022-05-25T14:17:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [May 25, 2022, 2:57pm UTC](https://forum.inductiveautomation.com/t/reporting-dynamic-chart-timespan/60010/2 "2022-05-25T14:57:48Z")

</div>

I would uses a script data source in the report to extract the appropriate subsets of the historion dataset and attach them to the traceability dataset as child keys (nested). Then you can use these child keys in the per-piece chart. This topic should help you do this:

> [@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/reporting-dynamic-chart-timespan/60010)._