In this section, you will learn how you can formulate such custom filter queries. You will see how to write simple expressions for filters on single asset fields and primitive attribute fields as well as how to nest field expressions using the primitive attribute members of a composite attribute. For more details on the search syntax, see The Model Manager Search Syntax in the Model Manager Reference Manual.

An asset filter consists of one or more field expressions combined with Boolean operators — for example, AND, OR, and NOT — and other grouping operators. Each field expression specifies which field and what field value is being filtered on.

You write an asset field expression using an @-notation of the general form:

with <field-name> equal to the name of one of the available asset fields in Table 4-3, and <field-value> the value being filtered on. Write, for example,

to find assets whose title contains the word crane. To match on several search words, enclose the words with parentheses. Write

to find assets whose title contains the words mounted and crane.

A space between two search words is automatically interpreted as a Boolean AND. The previous expression is thus equivalent to:

if you want to find assets whose title contain mounted or crane.

and matches on assets whose title or description contains the words mounted and crane, whose asset type is Project, and that was last modified by user Alice. The following is not valid:

with <attribute-identifier> equal to the identifier of a primitive attribute and <field-value> the value being filtered on. Write, for example,

to find all assets with the value planned for a hypothetical primitive attribute status of Keyword value type. Similarly, the expression

matches all assets with a range of values for a hypothetical primitive attribute week_estimate of Integer value type.

For primitive attributes with value types that support filtering on multiple fields, the above syntax automatically targets a default field. For an Attachment it is the filename, for a File version or Model version it is the item version’s title, and for a Link it is the link text. Write, for example,

to find all assets with an uploaded file truck mounted crane.pdf for a hypothetical Attachment primitive attribute with identifier product_manual.

with <attribute-identifier> equal to the identifier of the attribute and <field-name> equal to the name of one of the available fields in Table 4-4, Table 4-5, and Table 4-6. Write, for example,

A similar syntax is used when searching on the fields of File Version, Model Version, or Link attributes. Write, for example,

to find all assets linking to fileset versions via a hypothetical File Version primitive attribute with identifier auxiliary_data.

with <composite-identifier> equal to the identifier of a composite attribute, <primitive-identifier> equal to the identifier of a primitive attribute that is a member of the composite attribute, and <field-value> equal to the value being filtered on. Write, for example,

to find all assets with the values Paris and 2020 for the two primitive attributes, conference and year, belonging to the composite attribute journal_reference. This syntax is especially useful when you want to match on multiple cells in a table row corresponding to a composite attribute in Table mode. Write, for example,

to find all assets with a table row in a hypothetical models composite attribute table in which the model column has a model version title containing mounted crane, and the product_version column has the value 11.2.

The Model Manager server web interface automatically detects if your write an expression in a search or filter input field using a malformed search syntax. A warning banner with a message describing the problem is shown below the input field. The warning banner stays visible until you either correct the problem or click the Close button on the banner.