Describe the bug
We are using a global, script generated tree with following schema:
World
-> region
-> country
-> state
-> city
-> site
-> Cacti Device Type
-> Device
First off, the search will find matching objects. It doesn't matter if it is part of the device, site or city name, BUT
all elements belonging to a matching items will not be available in most cases.
Example:
You search for "Dear" and Cacti builds following tree:
->World
-> North America
-> US
-> Michigan
-> Dearborn
Leaf sites and assigned device types and devices are not part of the result. Matching City name "Dearborn" is not clickable and does not allow to load underlying elements with another call.
Describe the bug
We are using a global, script generated tree with following schema:
World
-> region
-> country
-> state
-> city
-> site
-> Cacti Device Type
-> Device
First off, the search will find matching objects. It doesn't matter if it is part of the device, site or city name, BUT
all elements belonging to a matching items will not be available in most cases.
Example:
You search for "Dear" and Cacti builds following tree:
->World
-> North America
-> US
-> Michigan
-> Dearborn
Leaf sites and assigned device types and devices are not part of the result. Matching City name "Dearborn" is not clickable and does not allow to load underlying elements with another call.