I encountered a bug where if I change the parent data type of a udt instance it does not update the sqlth_te database. I am currently stepping through removing the unused tags. Is there a clean way to add in all of the correct tags without just stepping through them one by one? I’m trying to save some time here. It’s looking like this might be the rest of my week
Hi Daniel you could try exporting the tags in Json format so that you are able to modify the tags with the UDT instances and make sure they contain the correct instances and definitions and then re-importing into the designer that way you don’t have to manual go through all the tags only change the ones you need too.
I can’t promise it’s a fully supported action, but in the past when I needed questional sqlth_te entries to stop being used, I manually set all of their retirement dates to slightly in the future and Ignition noticed and made new ones as needed. Multiple sqlth_te entries for the same tag are allowed, even on the same time span.
So you were able to set every tag in the sqlth_te database to retire slightly in the future, and the database recreated the necessary ones?
I didn’t hit EVERY tag with a retirement, but definitely more than I needed to. It was a group of like 1000 tags that were a mix of things I wanted to retire and things that were still being used, and Ignition automatically made new sqlth_te entries for the ones that were still being used. And querying the history on the tags that kept going includes history from both sqlth_te entries.