Not all of the historical tags are returning from the system.tag.browseHistoricalTags() command and I don’t see a difference in the tags that are returned from the ones that are not.
Database query results (Note both “L43-315” and “L99-987” string array tags)
|id|tagpath|scid|datatype|querymode|created|retired| |---|---|---|---|---|---|---| |2849|mes devices/l43-315|13|2|0|1559663140399|NULL| |2850|mes devices/l43-315|13|2|0|1559663140399|NULL| |2818|mes devices/l99-987|13|2|0|1558731853536|NULL| |2819|mes devices/l99-987|13|2|0|1558731853536|NULL|
SELECT * FROM dbo.sqlth_te T
WHERE (T.tagpath LIKE ‘mes devices/L99%’ OR T.tagpath LIKE ‘mes devices/L43%’)
AND T.retired IS NULL ORDER BY T.tagpath ASC
Test code to isolate the data from the script console:
t=system.tag.browseHistoricalTags(path=hp, nameFilters=['*l43*','*l99*']).getResults() for s in t: print s.getPath()
histprov:Ignition_TEST:/drv:ignition-lneist01:default:/tag:mes devices/l99-987 histprov:Ignition_TEST:/drv:ignition-lneist01:default:/tag:mes devices/l99-987
Note that “L43-315” is NOT in the data back from Ignition. Why not?
- scan class is the same
- data type is the same
- tags are not retired
- both tags currently have data in the string arrays
I am using a trial version for development and when I created the tags the gateway may have been timed out. I am unsure either way. I deleted the tag and re-created with the gateway running today after working this problem yesterday. This did not change the results.
Anyone else see this kind of problem?