Forum Discussion
As far as I know, properties will override and not append when set at various levels. The only exception I'm aware of is system.categories. It does appear to append the various levels together (I believe it's internally stored as an array). I would be careful not to overload with manual categories though, it's heavy involved with controlling what checks are applied to devices.
Can you cover in more general what you are looking to do? Perhaps there are other ways to implement what you are looking to do.
We have a module that uses a property to list out Windows Services that we want it to check and restart if they aren't working. We have some services we want checked at a global level and other services that would only be at a lower level.
If I have "Service1" I want checked everywhere, and "Service2" that I only care about on certain machines, I can add Service1 at root, but then I have to add "Service1|Service2" at the lower level to keep them both in there. If I only add Service2 at the lower level, it will currently overwrite Service1.
I didn't think there was a way around it, but thought if there was a syntax-type trick to make it append instead of replace, that'd be helpful.
- Joe_Williams2 months ago
Professor
We would accomplish this with two properties then. Something like windows.services.list at the root then windows.services.list.custom wherever else. Then you can just combine them in the datasource.
Related Content
- 30 days ago
- 4 years ago