Ignition 8.1.13
Weird use case, but…
- Create an empty tag folder named ‘PlaceHolder’
- Export just it to ‘PlaceHolder.json’
- Delete the tag folder.
- Import ‘PlaceHolder.json’
- The original folder ‘PlaceHolder’ is not recreated
-Shane
Ignition 8.1.13
Weird use case, but…
-Shane
Actually it looks like it imports the original folder under the UDT tab… which is probably “more wrong”.
Where was the focus in the tag tree when you began the import?
‘Tags’ tab active, right click top left area of of ‘Tag’ column.
Hi Just wanted to jump on this.
I have been playing with some proof of concept Tag structures In ignition and have come across the same issue. All folders are empty, and it was set up in ignition designer with great success.
My structure looks a bit like this
Now I wanted to expand it significantly and am lazy, so I.
The issue I am having returns the following error
To be clear there are no UDT’s in play - not even a tag involved - this is just empty folders
As per previous post - I also get a new UDT which matches my tag structure …say what!
please note the UDT is only created when I have focus nowhere on the tag browser- then use the top right drop down import to root Function, else nothing happens at all (except the error)
EDIT: you can copy said UDT folder structure out of the UDT area into the tag browser, so if you are manipulating folders only this may get you out of dodge.
I have tired having the focus in the tag browser
Luckily for me this is proof of concept - but it is a problem will hurt when I finalize the directory and want to back it up. I am also wondering what happens to any pre made empty folders on a full (working) tag tree backup.
If I have one empty folder nested somewhere on an entire project… what happens if I try to import it?
Any help or advice would be greatly appreciated.
I reckon there's already a bug reported for this - I've seen this before as well where empty folders simply aren't imported/created including when pasting JSON.
Found it: