# Report Module - tag history

**URL:** <https://forum.inductiveautomation.com/t/report-module-tag-history/107132>\
**Category:** Ignition\
**Created:** [June 6, 2025, 2:53pm UTC](https://forum.inductiveautomation.com/t/report-module-tag-history/107132 "2025-06-06T14:53:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cory\_Lambert](https://avatars.discourse-cdn.com/v4/letter/c/9fc29f/32.png) [@Cory\_Lambert](https://forum.inductiveautomation.com/u/Cory_Lambert)\
**Post date:** [June 6, 2025, 2:53pm UTC](https://forum.inductiveautomation.com/t/report-module-tag-history/107132/1 "2025-06-06T14:53:47Z")

</div>

I'm using a tag's historian as one of the data sources in a report. The tag is an expression that is intentionally null if certain conditions aren't met. The issue I'm having is that when I pull the tag's history into the report, it somehow assumes that I want the null values to be "0". I don't want the null values to be "0", I want the null values to be disregarded from the Basic Average aggregation that is being performed on this built in query.

Any suggestion on how to disregard null values from the tag history data source would be appreciated.

P.S. When I pull the tag into a power chart, it treats the null values at just that - null. There's no data for the time periods when the conditions aren't met for the tag to not be null.

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [September 30, 2026, 8:29pm UTC](https://forum.inductiveautomation.com/t/report-module-tag-history/107132/2 "2026-09-30T20:29:50Z")

</div>

Bumping this back up. I'm having a similar problem. We purposely built an expression tag that uses a null value based on another tag value in hopes that the data would be excluded from averages that way, but it doesn't make a difference. Values are being returned as 0s when queried, but if I query the database directly, I can see the null values in the table, so I know it's storing them properly they're just not being retrieved correctly. This is on 8.1 so not sure if 8.3 has fixed any of this with the new historical queries.