What's the thought about using custom properties in tag folders?

Ignition
1

Hi!

What about creating custom properties in the tag folders?

I mean, they don't show but they are there. You can add, deleted and read them. Could this cause any problem?
My testing doesn't show any problems, but if someone has any information or some idea about this would be nice to know.

Thanks!

2

I have no clue what you're talking about.
Folders ? For custom props ? How do you even make a folder in properties ?

3

I'm pretty sure OP is asking about tags.

If you don't mind the complete lack of discoverability, then sure, go for it. In 8.3 we added some extra 'meta' properties to folders to support alarm aggregation.

1 Like
4

I clarified the topic title by adding “tag” in front of “folder” (in case you thought you went crazy).

I've written properties to folders accidentally before. I'm not sure there's a good reason to do it.. Maybe if you don't like your co-workers :grinning_face:

1 Like
5

Yeah sorry, I mean tag folders not folders in properties.

English is not my original language and sometimes my head just messes all up :folded_hands:

6

To clarify this, I think what OP means is adding a custom key value pair to a folder like this:

#configure a folder with a custom property
config = {'tagType': 'Folder', 'name': 'This folder makes a noise', 'sound': 'boom'}
system.tag.configure('', config, collisionPolicy = "o")
#read the config back to see what it looks like
system.tag.getConfiguration('This folder makes a noise')
#read the property as a tag and get a fully qualified value back
system.tag.readBlocking(["This folder makes a noise.sound"])

you can get the value of the property by doing a tag read (dot notation on the folder) you can do a tag binding to this property as well.

Since this is completely hidden within the designer, I think this is a terrible idea. As Nick said, if you don’t like your co-workers, go wild.

1 Like
7

The main idea is not to see them :joy:

I wanna make an identification for the child tags without "messing" the tags with custom props