# Historian Tags in Version 7.7.10 -- Generating Report --

**URL:** <https://forum.inductiveautomation.com/t/historian-tags-in-version-7-7-10-generating-report/37740>\
**Category:** Ignition\
**Created:** [August 14, 2020, 5:52pm UTC](https://forum.inductiveautomation.com/t/historian-tags-in-version-7-7-10-generating-report/37740 "2020-08-14T17:52:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmonter](https://avatars.discourse-cdn.com/v4/letter/j/858c86/32.png) [@jmonter](https://forum.inductiveautomation.com/u/jmonter)\
**Post date:** [August 14, 2020, 5:52pm UTC](https://forum.inductiveautomation.com/t/historian-tags-in-version-7-7-10-generating-report/37740/1 "2020-08-14T17:52:12Z")

</div>

I have a customer using Ignition Version 7.7.10 and requires a set of reports to be generated based on some historian tags.  
His requirement is to pull data for a month (flow,ph, etc).

- Each Day Average
- Each Day Max, Min

I can retrieve the data but don’t know how to generate the average for each day and still pass the information to the report module.  
I’m thinking of retrieving all my data for a month pass it over to mySQL and do all my queries and calculations there but that seems clumsy and would take a lot of resources…  
Any ideas?  
Thanks.

---

<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:** [August 14, 2020, 5:59pm UTC](https://forum.inductiveautomation.com/t/historian-tags-in-version-7-7-10-generating-report/37740/2 "2020-08-14T17:59:51Z")

</div>

So many applications for my [Simulation Aids](https://inductiveautomation.com/moduleshowcase/module/automation-professionals-llc-simulation-aids) module today!

You probably want the grouping feature of the [view() expression function](https://www.automation-pros.com/simaids/doc/expression.view.html) to generate a separate dataset. Pass them both to the report module. (IIRC, v7.7’s reporting module runs only in the client. For v7.8 and later, I’d recommend a script data source to post-process the raw data.)
