# Montly Report with one-page Timeseries Chart per day **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [January 7, 2022, 10:27pm UTC](https://forum.inductiveautomation.com/t/montly-report-with-one-page-timeseries-chart-per-day/54791 "2022-01-07T22:27:14Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![zacht](https://avatars.discourse-cdn.com/v4/letter/z/ea5d25/32.png) [@zacht](https://forum.inductiveautomation.com/u/zacht)\ **Post date:** [March 8, 2023, 5:17pm UTC](https://forum.inductiveautomation.com/t/montly-report-with-one-page-timeseries-chart-per-day/54791/5 "2023-03-08T17:17:50Z")
It would look something like this example. Your parent query could return your daily bounds. Your child query would get the actual data. > [@Dynamic report creation or merging of reports](https://forum.inductiveautomation.com/t/dynamic-report-creation-or-merging-of-reports/62066/7): > > The top-level query should be where you compile your list of parameters. In the example below I’ve basically typed my list statically, but if you have a list in SQL you can perform a real query. QUERY (This returns one row called machines with values 1, 2, 3) You then create a sub-query. Change the type of the sub-query to Tag Historian Query. The tag path will contain a parameter in curly braces that matches the column name from the parent query. In my case, the path is: %PATH\_REDAC… --- _[View the full topic](https://forum.inductiveautomation.com/t/montly-report-with-one-page-timeseries-chart-per-day/54791)._