storeTagHistory() seems to be writing to DB but I cant see the inserted data anywhere

Ignition
1

I am using the function below to try to add data to my historian DB. When i run this in script console it seems to compile with no errors. I added a few lines to the script to query and print the historical data that i'm inserting and that comes back with no values. If i run it more than once for a date/time then i get a log message error saying that it could not insert because of a duplicate timestamp. I have a tag history table configured for this tag and I do not see any of the values that are supposedly being inserted into the historical database. What is going wrong here??

histProv = "Ignition_Hist"
tagProv =  "HIST_Dashboard"
paths = "[HIST_Dashboard]LYO 1/Unit Test/Alarm/LYO1_Phase1_LeakRate"
histDate = system.date.getDate(2024, 7, 17)
histDateTime = system.date.setTime(histDate, 10, 07, 44)
date = histDateTime
system.tag.storeTagHistory(histProv, tagProv, [paths], [6.9], [202],  [histDateTime])
2

The months in getDate are zero indexed - are you looking in the July partition, or the June one?

4

I was trying to view the tag history in a table component with date parameters but even with the dates wide open (like may to august) i am not seeing the values that I am writing. Next step will be to start digging through the partitions. I did see a log message that said a partition was created when I was first trying to write this data.
edit: we are writing data for 2024 because we do not currently have any data for this tag that old and i think thats why i saw a log that a partition was created

5

There is content about tagid, created, retired,https://www.docs.inductiveautomation.com/docs/8.1/appendix/reference-pages/ignition-database-table-reference#sqlth_te but I don't think that is very intuitive. I prefer not to use the storeTagHistory method, but to manually query the tagid, modify the created value, and then write the data to the table for the corresponding month.

6

So i can insert rows directly into a partition table from SQL? Is that what you are recommending? I cant edit existing entries because there are no existing entries for that tag id for the time period we wish to write data on

7

You can, because it's just rows in a database, after all. I would definitely not recommend it.

8

So you want to add historical data to your current history tables, which means you probably moved from one historian to another?

I have attempted to do this as well, with variable success, except to make sure the tag paths and id's match up in the new historian tables.

Could you run an import in your SQL manager into temp tables, clean the data to match tag paths and id's?

And like Paul said, dynamically renaming columns in the DB is a bad idea.