Skip to main content

Searching and Filtering Pretreatment Tables

How to run a quick search on one field, build an advanced filter, and combine the two on Pretreatment tables.

Overview

Every Pretreatment table has two ways to narrow it down: a quick search on a single field, and an advanced filter for multi-condition queries. They work together — you can apply one on top of the other. This replaced an older search bar that expected query syntax. If you remember typing conditions into the bar itself, that is gone; the bar is now a plain text search, and the query building has moved behind an icon.


Before you begin

📝 Make sure a field is selected. The search runs against the field chosen in the dropdown to the left of the search box. Most tables open with their default search field already chosen. If the dropdown is empty, pick a field first. Until a field is chosen, the Search button is disabled, and on some tables the box itself is too.


Searching one field

  1. Open the field dropdown to the left of the search box. It lists the searchable columns on that table (not every column can be searched); the table's default search field is marked with an asterisk.

  2. Choose the field you want to search.

  3. Type your text in the search box and press Enter, or select the Search button.

To undo it, select the Clear search (✕) control at the right of the box.


Building an advanced filter

For anything more than one field, use the builder.

  1. Select the Advanced Filter Builder icon beside the search box.

  2. Build your conditions in the window that opens.

  3. Select Apply Advanced Filter. The search runs and the window closes.

While an advanced filter is active, a badge on the icon shows how many conditions are in it, and a clear (✕) control appears beside the icon to remove them all.


Combining the two

The quick search and the advanced filter stack rather than replace each other:

  • Run a text search after an advanced filter, and it searches only the filtered rows.

  • Apply an advanced filter after a text search, and it filters only the searched rows.

So if a row you expect is missing, check whether both are active — the badge on the builder icon and the text in the search box each tell you.


Where this works

The same search bar and builder appear on the Pretreatment tables, including:

  • Industrial Users

  • Sampling Results

  • Permitting

  • Inspections

  • Violations

  • Response

  • Users

  • Limits, on both the Outfall Overview and Permit Overview pages

  • General Controls, under Configuration → POTW


What happens next

Searches and filters only change what you are looking at — nothing is saved or altered on the records themselves. If you find yourself rebuilding the same filter often, you can keep it: see Saving Filters on Pretreatment Tables.


Video walkthrough


FAQ

Why can't I type in the search box?

No field is selected. Pick one from the dropdown to the left of the search box. Until you do, the search can't run, and on some tables the box is disabled.

What does the asterisk next to a field mean?

It marks that table's default search field.

I used to type my whole query into the search bar. Where did that go?

That bar expected a specific query syntax, and most people reasonably expected a plain text search instead. The bar is now a plain search, and query building moved into the Advanced Filter Builder behind the icon beside it — nothing was lost.

A row I expect is missing from the table. Why?

Check whether both a text search and an advanced filter are active — they combine, so a search runs only against rows the filter already allowed. The badge on the builder icon shows how many filter conditions are applied.

Which fields can I search?

Only the columns that table makes searchable — mostly text columns, plus the active/inactive column on Industrial Users. The dropdown lists them by their column name.

Does searching change my data?

No. Search and filter only affect what the table displays.


Related articles

  • Saving Filters on Pretreatment Tables

  • Navigating an Industrial User Record

Did this answer your question?