# History binding returns unwanted data point

**URL:** <https://forum.inductiveautomation.com/t/history-binding-returns-unwanted-data-point/96054>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [September 17, 2024, 8:02am UTC](https://forum.inductiveautomation.com/t/history-binding-returns-unwanted-data-point/96054 "2024-09-17T08:02:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [September 17, 2024, 8:02am UTC](https://forum.inductiveautomation.com/t/history-binding-returns-unwanted-data-point/96054/1 "2024-09-17T08:02:58Z")

</div>

Hello folks,

I have a timeseries chart with a tag history binding, set up like this:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/1/21401433673df8f41bcabfefd8da4303ab3ba170.png)

The start and end date come from date pickers, configured to use 2023/12/01 and 2023/12/31 as defaults, because the sample data I have is for dec. 2023.  
2023\_12 is the only historian partition I have:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/7/e74defe3548bc2bc27a6c61bbdc115932c77b3db.png)

Here's what I get:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/2/f20e43328c7e4bbd97743c1711de5d5192b7bd67.png)

data up to now.  
Here's the last row of the dataset:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/8/38895aa20474770c3b3c78931aca56d0e7c91318.png)

There's a data point generated for now, which is really, really not what I want. For now I'll just remove the extra row in a transform, but I'd like to know if I can get a proper fix for this.

I'm on 8.1.43, and I don't recall ever encountering this before.

---

<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:** [September 17, 2024, 1:46pm UTC](https://forum.inductiveautomation.com/t/history-binding-returns-unwanted-data-point/96054/2 "2024-09-17T13:46:13Z")

</div>

Ignition's historian doesn't use half-open time spans. You have to subtract one millisecond from the start of the next day before using it in the history binding. Or in queries. (This is also true when using smaller intervals. The end timestamp must be the last millisecond in the last interval.)

See my Tag Report Utility's time span and history query handling in my exchange resource:

> [@Tag Report Utility](https://forum.inductiveautomation.com/t/tag-report-utility/95299):
>
> New resource just uploaded to the Exchange (pending review). Also available here: [https://www.automation-pros.com/TagReportUtility/](https://www.automation-pros.com/TagReportUtility/) I intend to publish at this link as well as in the Exchange going forward. Announcements will be in this topic. (: Highlights: Provides a Perspective Popup View that provides a user interface to system.tag.query() that entirely replicates the functionality of the Designer's Tag Report Tool. Provides a Perspective Embedded View that provides Time Span selectio…

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [September 17, 2024, 2:09pm UTC](https://forum.inductiveautomation.com/t/history-binding-returns-unwanted-data-point/96054/3 "2024-09-17T14:09:31Z")

</div>

But that's not the next day, that's a full year and a half after the end of my time window, and the data point returned doesn't exist anywhere.

I want data from december 2023, and I'm getting data that was never stored in the historian for today, september 17th 2024, and I get it anyway I configure the time range.

---

<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:** [September 17, 2024, 2:42pm UTC](https://forum.inductiveautomation.com/t/history-binding-returns-unwanted-data-point/96054/4 "2024-09-17T14:42:50Z")

</div>

Ah, that the "real time" point that gets injected for any tag using "Analog" deadband style. (Including "auto" that yields "analog" by data type.)

---

<div class="post-metadata">

**Author:** ![pascal.fragnoud](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pascal.fragnoud/32/24728_2.png) [@pascal.fragnoud](https://forum.inductiveautomation.com/u/pascal.fragnoud)\
**Post date:** [September 17, 2024, 2:46pm UTC](https://forum.inductiveautomation.com/t/history-binding-returns-unwanted-data-point/96054/5 "2024-09-17T14:46:41Z")

</div>

Those tags are not historized but injected directly into the historian with `system.tag.storetagHistory`, I probably should have mentioned that.  
ALL the data in that historian was put there manually, and NONE of the tags has any historization configured.
