Pipeline report filters for a coverage review include field boundaries, reusable report criteria, expected-closing date ranges and conditional expressions.
Key takeaways
- Set field boundaries: In the custom report builder, you can set limits and boundaries for the fields you have added to a report according to HubSpot.
- Choose a date range operator: When adding a new rule, select is between from the drop-down menu in the second field to define a date range according to Odoo.
- Locate custom expression controls: To use the custom expression editor, create a Custom Column or click on Filter or Summarize and select Custom Expression according to Metabase.
Pipeline report filters: the documented choices
The four documented tools for coverage reviews are the HubSpot custom report builder, EspoCRM Reports, Odoo Pipeline Analysis, and the Metabase query builder. Each tool documents distinct filtering mechanisms for selecting records during a pipeline coverage review.
In the HubSpot custom report builder, you select the report's data sources by choosing the types of HubSpot data that the report will include, according to HubSpot. You then add fields to the report by selecting the specific property, event, and activity data to report on, according to HubSpot. Finally, you customize report filters by setting limits and boundaries for the fields you've added, according to HubSpot. These three steps represent distinct configuration decisions: choosing data sources, adding fields, and setting filter boundaries.
EspoCRM supports report inclusion criteria, logical operators, and runtime filtering without editing the report. Its examples include a related-account age condition and an opportunity count greater than one, which are examples rather than recommended coverage thresholds.
Odoo documents default Pipeline Analysis filters and selecting Expected Closing with an is between operator before adding the custom filter.
Metabase documents conditional expressions, combined conditions, date-window examples, and conditional aggregations. Its sample field names and values are preserved rather than presented as sales benchmarks.
These filters select which records enter a report. The example amounts, dates, account ages, or opportunity counts are not recommended sales thresholds.
Compare filtering controls using each tool's documentation
Configuration decisions in a reporting tool separate into distinct steps. The first decision is which data the report examines. This step defines the scope of records available for the report.
The second decision is which attributes to add. After selecting data sources, you add fields to the report by selecting the specific property, event, and activity data to report on, according to HubSpot.
These two steps are separate configuration actions. Treating them as distinct decisions helps clarify what a report can and cannot show.
When reviewing pipeline coverage, the data source selection determines whether the report includes opportunity records, account records, or other entity types. The field selection determines which properties, such as amount or stage, appear in the report. A report built with one data source and a different set of fields can produce different results than one built with a different source or field combination.
The documentation for the custom report builder describes these as sequential steps in the report creation process. The first step is selecting data sources. The second step is adding fields. Each step requires a specific selection from the available options.
For a coverage review, the choice of data sources should match the entity type you are analyzing. If you are reviewing opportunity pipeline, the data source selection should include opportunity data. If you are reviewing account-level coverage, the data source selection should include account data. The field selection should then include the specific properties relevant to your review, such as deal amount, close date, or stage.
Filter controls reference table by publisher
| Publisher | Documented Filtering Control | Source Page Title |
|---|---|---|
| HubSpot | Select report data sources | Create reports with the custom report builder |
| EspoCRM | Define report inclusion criteria | Reports - EspoCRM Documentation |
| Odoo | Inspect default analysis filters | Expected revenue report — Odoo 18.0 documentation |
| Metabase | Locate custom expression controls | Custom expressions - Metabase Documentation |
HubSpot documents selecting the types of data included in a report, according to HubSpot. EspoCRM describes specifying criteria in the Filters section that determine which records are included, according to EspoCRM. Odoo notes that the Pipeline Analysis dashboard includes several filters in the search bar by default, according to Odoo. Metabase explains how to use the custom expression editor with a Custom Column or by selecting Custom Expression in Filter or Summarize, according to Metabase.
HubSpot field boundaries and EspoCRM runtime criteria
HubSpot separates choosing report data sources, adding fields and setting filter boundaries as distinct configuration decisions. These steps define which records enter the report and which data it reports on.
EspoCRM documentation describes how to define report inclusion criteria and narrow results at runtime. In the Filters section, you can specify criteria that determine what records will be included in your report, according to EspoCRM. The system supports logical operators 'OR' and 'AND' to combine these filter conditions, according to EspoCRM.
Runtime Filters lets you narrow down the results each time you run the report, without needing to edit the report itself, according to EspoCRM. This mechanism allows for dynamic record selection during a coverage review. The documentation provides specific examples of filter conditions. One example filters records that were created after less than 12 month from the creation of a related account, according to EspoCRM. Another example uses the condition COUNT / opportunities.id / Greater Than / 1, according to EspoCRM.
These examples illustrate the syntax and structure of available criteria. They are not recommended sales thresholds or coverage multiples. The related-account age condition and the opportunity count greater than one serve as demonstrations of how logical operators and field relationships function within the report builder. When configuring your own coverage review, identify the specific fields and conditions that select the records you need to inspect. Use the logical operators to combine multiple criteria if your review requires narrowing by several attributes simultaneously. The runtime filtering capability means you can adjust these selections for each review session without altering the underlying report definition.
Inspect the inclusion criteria for your next coverage review and identify the fields and conditions selecting its records.
Odoo closing-date ranges and Metabase expressions
The Expected revenue report — Odoo 18.0 documentation describes a workflow for narrowing records by expected closing dates. The Pipeline Analysis dashboard includes several filters in the search bar by default, according to Odoo. To create a custom range, enter Expected Closing in the Search… bar or pick it from the list, according to Odoo. In the second field of the new rule, select is between from the drop-down menu, according to Odoo. At the bottom of the Add Custom Filter form, click Add, according to Odoo. This sequence defines the boundaries for the records included in that specific view.
Metabase documentation offers a different mechanism through custom expressions. The Custom expressions | Metabase Documentation page details how to write conditional logic directly into queries. For example, you could write [Subtotal] + [Tax] < 100, according to Metabase. This expression combines arithmetic and comparison operators to filter records based on calculated values. Another documented example is Share([Total] > 50), which would return the percentage of orders with totals greater than 50 dollars, according to Metabase. These examples illustrate the syntax for conditional aggregations and arithmetic comparisons. The field names [Subtotal], [Tax], and [Total] are specific to the Metabase documentation examples and do not represent standard sales field names across all systems. When using these tools, verify that the field names in your data source match the syntax required by the expression builder.
For your next coverage review, inspect the inclusion criteria in your reporting tool. Identify the specific fields and conditions selecting the records you plan to analyze. If you use Odoo, check the default filters in the search bar before adding a custom date range. If you use Metabase, review the expression syntax to ensure your conditional logic matches your data structure. These steps help you understand which records are visible in your current view.
Illustrative example: a review filter
A reviewer keeps open records with an amount above 100 and a closing date within 3 months, then checks 20 of the 50 records returned.
Which filtering approach fits your review task
Matching a filtering method to a specific coverage review task depends on whether you need to inspect combined logical conditions, apply functions within aggregations, or evaluate alternative date windows. The documentation for Custom expressions | Metabase Documentation outlines how to construct these specific queries. For instance, you can read a combined condition example where the expression is [Subtotal] < 100 AND [Tax] > 12 according to Metabase. This specific syntax demonstrates how to join two distinct field comparisons using the AND operator within a single filter rule.
When your review requires counting or summing records based on complex logic, inspect the conditional aggregation examples. You can use functions inside of the conditional portion of the CountIf and SumIf aggregations, like so: CountIf( round([Subtotal]) > 100 OR floor([Tax]) < 10 ) according to Metabase. This capability allows the filter to apply rounding or flooring functions directly to the field values before evaluating the condition. It supports reviews that need to categorize records based on calculated thresholds rather than raw stored values.
If your coverage review focuses on temporal patterns, read the alternative date windows provided in the documentation. The documented date-window example would return rows where Created At is between January 1, 2020 and March 31, 2020, or where Received At is after December 25, 2019, according to Metabase. This example illustrates how to combine a date range check with a "greater than" date check using the OR operator. It is useful for identifying records that fall into specific historical windows or those that meet a minimum date threshold.
Next step: list the filters your current pipeline report uses before your next review.
FAQ: Choosing filters for a coverage review
Which pipeline report filters do these tools document?
The documented choices include field boundaries, reusable report criteria, expected-closing date ranges and conditional expressions. The custom report builder allows selecting the types of HubSpot data that the report will include, according to HubSpot. The Filters section specifies criteria that determine what records will be included in your report, according to EspoCRM. To use the custom expression editor, create a Custom Column or click Filter or Summarize and select Custom Expression, according to Metabase.
Can I narrow an EspoCRM report each time without editing it?
Yes, Runtime Filters lets you narrow down the results each time you run the report, without needing to edit the report itself, according to EspoCRM. This control operates separately from the static criteria defined in the Filters section, which determine what records will be included in your report, according to EspoCRM. You can apply these runtime adjustments during the review process without modifying the underlying report structure.
How do I select an expected-closing date range in Odoo?
Enter Expected Closing in the Search… bar, select is between in the second field of the new rule, and click Add at the bottom of the Add Custom Filter form, according to Odoo.
Which Metabase examples combine conditions or date windows?
The documentation provides an example of a combined condition using the expression [Subtotal] < 100 AND [Tax] > 12, according to Metabase. It also illustrates alternative date windows with an expression that would return rows where Created At is between January 1, 2020 and March 31, 2020, or where Received At is after December 25, 2019, according to Metabase. These examples demonstrate how to structure logical operators and date comparisons within the custom expression editor, according to Metabase.
Does this comparison establish which filtering features my tool plan includes?
No, this page covers filter steps, not subscription tiers or pricing models. Verify your current plan details directly with your vendor to confirm which filtering capabilities are available in your environment.