I have a timeseries chart with a tag history binding, set up like this:
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:
data up to now.
Here's the last row of the dataset:
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.
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:
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.
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.
