When choosing a parent or child for a dependency, the search function automatically filters the results by the first alphabetical vendor and does not search the rest of the database if the node you're looking for is not found. In order to find the node you're looking for, you have to manually choose [No Grouping] and search again. It's a very minor thing but it creates a lot of unnecessary work when hundreds of dependencies need to be created.
The search in "Manage Nodes" is a good example of how all search functions in Orion should behave because it not only searches the entire database for the node you query, but it also remembers which grouping you viewed last time you used it. This is extremely useful when working with a large number of remote sites. For example if a change needs to be made to the router at every remote site, the search function remembers that you grouped your query by a specific custom property such as location or device type.
