Who this article is for: Org/City Users
Overview
The Advanced Filter Builder gives you full control over how you search and sort your assembly data. Instead of basic single-condition filtering, you can combine multiple criteria, group conditions together, and use AND/OR logic to build filters as simple or as detailed as your needs require — from a quick one-condition search to complex, nested filter logic across multiple fields.
Before You Begin
A few things to know before using the Advanced Filter Builder:
Where to find it. Click the Advanced Filter option on the Assemblies page to open the filter panel.
Filter conditions have three parts. Every condition requires a Column (the field to filter on), an Operator (how to compare), and a Value (what to look for).
Some fields behave differently than expected. Fields that appear as dropdowns in the main UI — like Hazard, Type, or Make — will show as plain text fields in the builder. You'll need to type the value manually rather than selecting from a list.
AND vs. OR matters. When combining multiple conditions, AND requires all conditions to match, while OR requires just one. Make sure you understand the difference before building complex filters.
Save filters you'll reuse. If you build a filter you'll need again, save it so you don't have to rebuild it from scratch next time.
Using the Advanced Filter Builder
The Advanced Filter Builder lets you create powerful, custom filters to find exactly the data you're looking for. You can combine multiple conditions, group them together, and use AND/OR logic to build filters as simple or as detailed as you need.
This guide walks you through everything — from adding your first filter to building complex grouped conditions.
Getting Started
To open the Advanced Filter Builder, click the Advanced Filter option. This opens a panel where you can start building your filter.
Adding a Filter Condition
Each filter condition has three parts:
Column — Pick the field you want to filter on (e.g., "Type," "Make," "Install Date")
Operator — Choose how to compare the data (e.g., "contains," "equals," "greater than")
Value — Enter the value you're looking for
For example: Make → equals → Wilkins/Zurn would show only rows where the make is "Wilkins/Zurn."
Understanding AND vs. OR
When you have more than one filter condition, you need to tell the system how to combine them. That's where AND and OR come in.
AND means all conditions must be true. Think of it as "this AND that must both match."
OR means any condition can be true. Think of it as "this OR that — either one works."
Example: AND
Show me assemblies where Type equals DC AND Make equals Wilkins/Zurn
This only returns assemblies that are both DC type and made by Wilkins/Zurn. If an assembly is a DC but made by a different manufacturer, it won't show up.
Example: OR
Show me assemblies where Type equals DC OR Type equals RP
This returns assemblies that are either DC or RP type. As long as one of those conditions is true, the row shows up.
Using Groups
Groups let you combine AND and OR logic together in the same filter. This is where things get really powerful.
How to Add a Group
In the filter builder, look for the option to add a group.
Each group has its own AND/OR toggle — so you can set whether the conditions inside that group all need to match (AND) or just one needs to match (OR).
You can have multiple groups, and the groups themselves are connected by the AND/OR logic at the level above them.
💡 Tip: You can add filters within a group by selecting the + icon in the same line as the AND/OR for that group:
Example: Groups in Action
Let's say you want to find assemblies made by Wilkins/Zurn and that are either DC or RP type. Here's how you'd set that up:
Top level: AND
Make equals Wilkins/Zurn
Group (OR):
Type equals DC
Type equals RP
This reads as: "Show me assemblies where the make is Wilkins AND the type is either DC or RP."
Without groups, you couldn't mix AND and OR logic like this — you'd get incorrect results.
Using Multiple Groups
You can also use multiple groups side by side. For example:
Top level: AND
Group (OR):
Make equals Wilkins/Zurn
Make equals Watts
Group (OR):
Type equals DC
Type equals RP
This reads as: "Show me assemblies where the make is Wilkins or Watts, AND the type is DC or RP." Both groups must be satisfied, but within each group, only one condition needs to match.
Nesting Groups Inside Groups
For even more complex scenarios, you can put a group inside another group. Here's an example:
Top level: OR
Make equals Watts
Group (AND):
Make equals Wilkins/Zurn
Group (OR):
Type equals DC
Type equals RP
This reads as: "Show me all assemblies made by Watts, OR assemblies made by Wilkins/Zurn but only if they're a DC or RP type."
Notice how the inner OR group is nested inside the AND group. This lets you say "Wilkins/Zurn AND one of these types" without that type restriction applying to Watts assemblies. Watts assemblies show up regardless of type, while Wilkins/Zurn assemblies only show up if they're also a DC or RP.
You can keep nesting groups as deep as you need, but for most use cases, one or two levels of grouping is plenty.
Filter Types and Their Options
Different types of columns give you different filtering options. Here's a breakdown of each type and what you can do with it.
Text Fields
Text fields are things like names, addresses, descriptions — anything with words or characters.
Option | What It Does | Example |
Contains | Finds rows where the field includes the text you type, anywhere in the value | Searching "Oak" would match "123 Oak Street" and "Oakland Ave" |
Does not contain | Finds rows where the field does not include the text you type | Searching "Oak" would exclude "123 Oak Street" |
Equals | Finds rows where the field is an exact match to what you type | Searching "Active" would match "Active" but not "Inactive" |
Does not equal | Finds rows where the field is anything other than what you type | Searching "Active" would show everything except "Active" |
Is blank | Finds rows where the field has no value at all | Shows rows where nothing was ever entered in that field |
Is not blank | Finds rows where the field has any value | Shows rows where something — anything — was entered |
Note: Text searches are not case-sensitive. Searching for "portland" will match "Portland," "PORTLAND," and "portland."
💡Heads up: Some fields that appear as dropdowns in the main UI (like Hazard, Type, or Make) will show up as plain text fields in the Advanced Filter Builder. The builder doesn't support dropdown selection for these fields — you'll need to type the value in manually.
Tip: Using contains instead of equals can make this easier, since you don't have to type the full value exactly. Just be careful — if multiple options share similar text, contains will match all of them. For example, if your hazard options include "Fire Sprinkler Chemical" and "Fire Sprinkler Wet," searching contains "Fire Sprinkler" would return both. Make sure the text you enter is specific enough to match only what you're looking for.
Date Fields
Date fields are things like install dates, inspection dates, due dates — anything tied to a specific day.
Option | What It Does | Plain-English Meaning |
= (Equals) | Matches the exact date you pick | "Show me items from this specific date" |
!= (Does not equal) | Matches everything except the date you pick | "Show me everything except this date" |
< (less than) | Matches dates before the date you pick | If you pick March 1, it shows February 28, February 27, and so on — but not March 1 itself |
> (greater than) | Matches dates after the date you pick | If you pick March 1, it shows March 2, March 3, and so on — but not March 1 itself |
<= (less than or equal) | Matches the date you pick and anything before it | If you pick March 1, it shows March 1, February 28, February 27, and so on |
>= (greater than or equal) | Matches the date you pick and anything after it | If you pick March 1, it shows March 1, March 2, March 3, and so on |
Is blank | Finds rows where no date was entered | Useful for finding records that are missing a date |
Is not blank | Finds rows where a date exists | Useful for finding records that have a date filled in |
Tip: "Less than" and "Greater than" for dates means "before" and "after" — think of earlier dates as smaller and later dates as larger.
True/False Fields
Some columns have values that are either one thing or the other — true or false, pass or fail, yes or no, checked or not checked. In the filter builder, these are called boolean fields.
For example, "Last Test Result" might show as "Pass" or "Fail" in the table, but behind the scenes it's stored as true (pass) or false (fail). The filter options reflect that.
Option | What It Does |
Is true | Shows rows where the value is true (e.g., compliant, pass, yes) |
Is false | Shows rows where the value is false (e.g., non-compliant, fail, no) |
Is blank | Shows rows where no value has been set |
Is not blank | Shows rows where a value exists (either true or false) |
Example: To find all assemblies that failed their last test, filter Last Test Result → is false. To find assemblies that are in compliance, filter Overall Compliance → is true.
Tips and Best Practices
Start simple. Add one or two conditions first, check your results, then add more if needed.
Use groups when mixing AND and OR. If you need some conditions to all be true and others where any can be true, groups are the way to do it.
Check your results after building. Complex filters can sometimes be tricky. If you're not seeing what you expect, review your AND/OR logic and make sure the groups are set up the way you intended.
"Is blank" is your friend. Use it to find records with missing data — great for data cleanup.
Save your filters. If you've built a filter you'll use again, save it as a view so you don't have to rebuild it every time.