Nav bar collections - xml option for search names not matching a string?

[Runals]

I'd like to create two different top level nav bar drop downs that both contain searches. I know there is the capability to include objects like saved searches that match a string (eg., match="error"). Is there a capability to define searches that don't match a string?

The use case is I'm turning over an app to some users where I will likely be adding additional searches in the future that deal with a specific topic and can use a common naming convention. At the same time I'd like for any searches they create to show up under a different nav bar dropdown w/o them having to conform to a specific naming convention.

[jonuwz · Accepted solution]

Looking in the code it looks like setting source="unclassified" will only pull in views that have not already been added to the menus.

./lib/python2.7/site-packages/splunk/appserver/mrsparkle/controllers/view.py line 247ish

So setting your defined views 1st, should exclude them from the dynamically created menu

see also the docs