ER Filtering


Related information: Adding a filter to a report

Below are some common ways to filter Enhanced Reporting data.

Filter criteria

The difference between is blank and is null

When to use the is blank or is null filter will depend on the dimension that you're filtering by. Some dimensions will include no data (null ∅), others will include a blank instead where it's not allowed to have a ∅ value.

Generally when choosing which filter to use, it is recommended that when you see ∅  to filter by is not null or is null and where you don't see anything at all, use is not blank or is blank.

Filtering by the logged in user

It is possible to apply a custom filter to a dashboard to limit information shown based on the logged in user.

Each user in the PageUp system has an internal employee_id (or provider_id) which is used for things like permissions, teams, etc. This can be used to filter the results in a report by using the relevant Provider ID field.

Example: Filtering by your job approvals.

  1. From the field listing, click to expand the Job: Approver group.
  2. Click to expand z_Primary Keys.
  3. Mouse hoverProvider ID and click Filter by field.
  4. In the Filter section, set the Job Approver - Provider ID criteria with:
    • matches a user attribute
    • Employee ID (null) - the null will soon populate with your ID
  5. Click Run to test the report.

Note: The purpose of this filter is to make the report more relevant for yourself, but it does not prevent users from changing or removing the filter.


There is an additional section in the field picker of every explore called "**Current User**" which has key attributes of the current logged on user to help with additional filtering.

These fields can be used in custom filters as follows

Examples of common custom logged in user filters:

Where the user running the report is the recruiter on the job.

${provider.provider_id} = ${current_user.provider_id}

Where the user running the report is the Hiring Manager on a job.

${requestprovider.provider_id} = ${current_user.provider_id}

Where the user running the report is the Reports to manager on a job.

${reportstoprovider.provider_id} = ${current_user.provider_id}

Where the user running the report is the onboarding delegate listed on the offer.

${OnboardingTaskProvider.provider_id} = ${current_user.provider_id}

Custom filters

We have released a feature whereby all reports have the filters permanently enabled on launch of the report, even for read only users, allowing you to easily change filters and rerun the report with the new filters applied.

Note: If the filters contain a Custom Filter as in the example above, this will not be editable at execution time, and the report creator/editor may use this to restrict data.

To add: in the Filter section, select the Custom Filter checkbox.
The Custom Filter text area displays - you may need to scroll down to see it.

Here are some common examples of converting a filter into a custom filter:

A string field is equal to a certain value.

A  field is filtered out to not null values.

A string field has to contain two other string values.

Custom filters allow for very powerful expressions which can be used in conjunction using AND and OR, and allow for string, numeric and date calculations and filtering.

For more information refer to the Looker documentation: Looker functions and operators.

Date filters

The following scenario will assist in deciding which date filter to use for your requirements:

If you want to report on data where [date field] is in the last day, and you will schedule the report at 6am every day. Remember that recent events may not be in the system as data may take 15-45 minutes to display in reports.

Date Filter for Yesterday

To set a date filter to focus on yesterday, you can use the matches (advanced) option to equal yesterday.

Other shortcuts include:

  • today
  • tomorrow
  • {n} {interval} from now (3 days from now)
  • {n} {interval} from now for {n} {interval} (3 days from now for 2 weeks)