# Report timeseries chart: issue to show raw values

**URL:** <https://forum.inductiveautomation.com/t/report-timeseries-chart-issue-to-show-raw-values/88774>\
**Category:** Ignition\
**Created:** [April 13, 2024, 11:50am UTC](https://forum.inductiveautomation.com/t/report-timeseries-chart-issue-to-show-raw-values/88774 "2024-04-13T11:50:44Z")\
**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:** [April 13, 2024, 1:34pm UTC](https://forum.inductiveautomation.com/t/report-timeseries-chart-issue-to-show-raw-values/88774/2 "2024-04-13T13:34:15Z")

</div>

This has nothing to do with reporting. You are mis-using the historian. It isn't designed to correlate your "batch active" tag with any other tag. Or any tag with any other tag. It has no way to query your tags with conditions from other tags.

The best you can do with the historian is to query in two layers: first query "batch active" to find the time boundaries of your batches, then repeatedly query your other tags for each time span. Reporting has no tool to do this for you, but you can use a report script to construct it. See this topic if you must use this route:

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

But the proper solution would be to use transaction groups to record into a conventional database table using your batch active tag as a trigger. Include the other desired data as columns in that transaction group. Then you can use conventional queries to access the data for your report.

{ One other note: the historian's "wide" return format is incompatible with "as stored" results. Use tall format. }

---

_[View the full topic](https://forum.inductiveautomation.com/t/report-timeseries-chart-issue-to-show-raw-values/88774)._