Bump. Any ideas here?
The chart resource is ambiguous to the view it is on, I think here is where the overall problem lies. When you are editing the resource, it will allow you to search the entire database as at that point it's not looking at the node you are looking at in your view. While it's a tedious task to add them in, that is, from my experience, how it is designed. One option that might help is creating custom properties on your interfaces and nodes, that you could then use as search criteria to help find what you are looking to add faster.
Loop 1 Systems