I've been using nested UDT folders for sorting UDT's by specific companies and locations since I have a variety of programs to manage. This hasn't been an issue until today when I created a new UDT folder in an existing group:
Folder Structure for UDT
-CompanyA
--SiteA
--SiteB
--NEWSITE
When I imported a group of UDT's into the NEWSITE folder I can no longer see the CompanyA folder when I go to create a new tag based on that UDT. I've tried removing the new UDT's, deleting the CompanyA folder and remaking it, even restarting the whole server Ignition is running on. The CompanyA folder still doesn't show up when I go to make a new tag. I tried making a whole new UDT folder and I can see that one after I add a UDT tag to it but the CompanyA folder is still missing. I can see it just fine when I'm looking in the UDT Definitions list.
I'm running 8.1.19 (b2022072711)
We can't see you screen, and you haven't shared any hard details, so can only speculate. To start:
-
Are you using more than one tag provider?
-
If so, are you sure you imported in to the tag provider where you are trying to make tags?
-
Have you refreshed the tag browser?
I have 3 tag providers setup. Default, Edge, MQTT Engine.
I had the default tag provider selected when I imported the UDT's using interactive import.
I have refreshed the tag provider. I have noticed other times when I delete a UDT folder that the only way I could get the empty folder to disappear was to restart Ignition completely.
More Updates
It looks like if I rename the top folder, in this case from "Select" to "Select1" the folder now appears using the new name. If I change the name back to the original "Select" then the new folder name and structure persists but all UDT elements are missing when I go to browse it. Another interesting note. If I edit a UDT in the "Select" folder, the tags I have made from it do update even though I can't see the folder to make a new tag from it.
Sounds like a bug. Consider setting up a test server with latest Ignition in trial mode, and restore this gateway's backup to it. And see if you can reproduce. If so, you should report it to support. If you can't reproduce, consider upgrading your production system.
Yeah I'll have to do that. The best I can do for now is rename the "Select" folder to "Select1" and all the created tags updated to show the new UDT parent data type name. Not ideal but it works for now. The only thing that I can think of that went different on this UDT import was a non-supported data type was set for one of the tags and it threw an error but let me finish the import. I just deleted the offending tag and didn't catch the issue till I tried to use it. I've had that happen before just didn't get this outcome. Thanks for the help!