The condition builder uses two different types of OR conditions: top-level and
Using a dependent OR condition, you can specify alternative criteria to a single operation.
Dependent OR conditions work in the manner A and (B or C). When you have an OR condition in
the query, the magnifying glass is no longer available. The conditions you put in the quick
search headers are ANDed together. Having an OR makes it ambiguous as to where the new
condition should go, for example before the OR, or after the OR.
For example, to return a list of all unassigned problem and incident records from the Task
table, create a filter with a dependent OR on the Number
- [Assigned to] [is] [empty] AND [Number] [begins with]
[PRB] OR [Number] [begins with] [INC].
A top-level OR condition allows you to display the results of multiple filter criteria in a
single list. Top level OR conditions work in the manner (A and B) or (C and D).
For example, to return a single list of all active incidents with a category of hardware, and
all inactive incidents with a category of software, create two condition sets separated by a
top-level OR condition.
- [Active] [is] [true] AND [Category] [is]
- Top level OR condition
- [Active] [is] [false] AND [Category] [is]
In List v3, select the New Criteria button in the condition builder to
create a new top-level OR condition.
Top-level and dependent OR conditions can be used together. Filters using both types of OR
conditions work in the manner (A or B) or (C or D). By mixing AND conditions with top-level
and dependent OR conditions, you can create very specific filters.