Nested Queries
For more powerful queries, use the results of a filter as the value of a predicate. This technique is called a nested query.
For example, suppose that you want to identify all the parts that originated from surface wrapper operations.
The initial query would resemble what is shown below. The query uses a property predicate from the Operation property of a mesh operation part, with all surface wrapper operations selected. The query results list all parts that are generated by surface wrapper operations.

However, if you create another surface wrapper operation, it would not appear in the results automatically. Select it manually in the value of the property predicate.
In the example below, SurfaceWrapper - SprueCup has been added manually to the query.

To avoid manual adjustments to filters, use nested filters as shown in the following example:
- Create a filter called
Filter-SW-Operations, using a Type predicate by dragging a surface wrapper operation node into the query filter.
- In the original query (named
Filter 9 in this example), change the value from a set of selected operations to the filter
Filter-SW-Operations.

To test if this filter automatically picks up new surface wrapper operations, make a few copies of the existing operations and see that the new ones show up immediately.