Introduction

Many consoles and tabs across PqW and PrW use a shared grid framework to display data. In addition to server-side filters (which query the database before data is loaded), these grids also support column filters — per-column filter controls built into the grid's column headers that allow you to refine data that is already loaded in the grid.

Column filters are different from server-side filters (which query the database directly). Column filters work on the client side — they filter the records that have already been fetched and displayed in the grid. This makes them ideal for quickly narrowing down visible data without making another server call.

This article explains:

• What column filters are and how they differ from server-side filters
• Where column filters appear
• How to access and use column filters
• What filter operators are available for different data types
• How to apply, view, and reset column filters
• Important behaviors and considerations

This is a generic reference article. The specific columns and filter options available will vary by console, tab, and grid — refer to the article for each console for details.

How Column Filters Differ from Server-Side Filters

Both filter types can be used together. For example, you might use server-side filters to load only records for a specific Account, and then use column filters to further narrow down by a specific Stage or Part Number within those results.

Where You'll See Column Filters

Column filters are available on virtually every grid across PqW and PrW. The behavior of column filters is consistent across all of these grids — once you learn how they work in one grid, the same principles apply everywhere.

Understanding Column Filters

Each column in the grid has a filter icon (typically a small funnel or filter symbol) in the column header. Clicking this icon opens a filter popup for that specific column.

The filter popup contains:

• Operator selector: A dropdown to choose how the filter value should be matched (e.g., Equals, Contains, Is Empty). The available operators depend on the data type of the column.
• Value field: Depending on the column type, this is either:
  • A text input box (for text and numeric columns) where you type the value to filter by
  • A dropdown / picklist (for picklist columns like Stage, Item Type, End Customer Request) where you select one or more values from a predefined list
  • A date picker (for date columns like Expiration Date) where you select or enter a date

• Save button: Applies the column filter to the grid. 
• Delete/Clear button: When you need to clear current selection and select different values
• Cancel / Close button: Closes the filter popup without applying changes.

Filter Operators

Each column filter has an operator that controls how the filter value is matched against the data in that column. The available operators depend on the data type of the column:

Text filters (e.g., Part Number, Description, Account Name, Manufacturer, Assignee):

Numeric filters (e.g., Quantity, VAR Total Profit, Customer Extended Price, List Price):

Dropdown / Picklist filters (e.g., Stage, Item Type, End Customer Request, Subscription Type):

These filters present a list of values derived from the data currently loaded in the grid. You can select one or more values from the list. When no values are selected (0 options selected), all records are shown.

Date filters (e.g., Expiration Date, Service Begin Date, Service End Date):

Reference filters (e.g., Account, Renewal Project, Internal Contract — lookup fields):

Reference filters typically support the same operators as text filters (Equals, Contains, Does Not Contain, Is Empty, Is Not Empty), filtering against the Name field of the referenced record by default.

Step-by-Step: Applying Column Filters

Step 1 – Load Data in the Grid

Before using column filters, ensure data is loaded in the grid. If your console has server-side filters, apply them first to load the relevant dataset. Column filters work only on the data that is already loaded — they cannot filter records that have not been fetched. For instance, here is the snapshot of Renewal Manager Console with default server-filters applied.

Step 2 – Click the Filter Icon on a Column Header

Locate the column you want to filter and click the filter icon in the column header. A filter pop-up will appear.

Step 3 – Select the Operator

In the filter popup, choose the appropriate operator from the dropdown. The default operator is typically "Equals" (Is Equal To).

Step 4 – Enter or Select the Filter Value

• For text/number columns: Type the value directly into the input field.
• For dropdown/picklist columns: Select one or more values from the list. Use the search box (if available) to quickly find a value.
• For date columns: Enter or select the date using the date picker or input field.

For example, in the Renewal Project console, the Renewal Date filter is a date field. Based on the requirement, you can enter values from the calendar.

Step 5 – Click Save

Click the Save button in the filter pop-up. The grid will immediately update to show only the records that match the filter criteria. The record count displayed in the grid will update to reflect the filtered results, and the filter icon turns red on the columns in which the filter is applied.

Step 6 – Apply Additional Column Filters (Optional)

You can apply filters on multiple columns simultaneously. Each additional column filter further narrows down the visible records. All active column filters work together (AND logic) — only records matching all applied column filters will be displayed.

Step 7 – Removing a Column Filter

To remove a column filter:

• Click the filter icon on the column header again.
• Clear the filter value (delete the text, deselect all picklist values, or click the ✕ icon).
• Click on the delete icon to clear the filters.

The grid will update to show all records (subject to any other active column filters or server-side filters).

Alternatively, click on the Reset Filter button in the Action toolbar. This will remove all the filters, including server-side and column filters, and the console will reload with the default filter values.

Important Behaviors and Considerations

• Column filters work on loaded data only: If the grid uses chunked loading, column filters apply only to the records currently loaded. Records on unloaded chunks will not be filtered. To filter across the entire dataset, use server-side filters or load all records first.
• Interaction with server-side filters: When you reset or change server-side filters and click Apply, the grid reloads data from the server. Be aware that column filters may be reset when the server-side data is refreshed. After changing server-side filters, re-apply any column filters as needed.
• Interaction with Load All / Load More: If you apply a column filter and then use "Load All" or "Load More" to fetch additional records, the column filter may be reset. Re-apply the column filter after loading additional data.
• Grouped data: When the grid has grouping enabled (e.g., grouped by Renewal Project or Parent Instance Number), column filters apply across all groups. However, in some cases with multiple levels of grouping, column filtering may not work for all fields — refer to the specific console documentation for known limitations.
• Record count: After applying a column filter, the record count shown in the grid reflects the number of filtered (visible) records, not the total number of loaded records.

Summary

Column filters are a flexible and convenient feature available across PqW and PrW grids. They allow you to quickly refine the data already displayed in the grid by filtering on individual columns using operators appropriate to each data type. When used in combination with server-side filters, column filters give you precise control over the records you see — use server-side filters to load the right dataset, and column filters to zero in on exactly what you need.

For details on which specific column filters are available on each console or grid, refer to the dedicated article for that console.