---
title: "Blank vs Empty in Workday Report Filters — Kiweely"
description: "Workday uses is blank for text, date, and Boolean fields, and is empty for instance fields. Wrong operators and optional prompts explain missing report rows."
url: https://kiweely.com/guides/workday-blank-vs-empty-report-filter-prompts
---

# Blank vs. Empty in Workday Report Filters and Condition Rules: Why Your Filter Misses Rows

Workday exposes is blank for text, date, and Boolean fields, and is empty for single-instance and multi-instance fields. Mixing those operators, treating a space as blank, or using a required blank prompt instead of ignore-if-blank are the usual reasons filters miss rows.

-   **Checked** against Workday on November 13
-   Applies to **Workday Reporting**
-   5 min read
-   Published November 13
-   By Kiweely

Workday does not use one universal “null” operator across every field type: text, date, and Boolean filters use **is blank** / **is not blank**, while single-instance and multi-instance filters use **is empty** / **is not empty**. Choosing the wrong emptiness test, leaving a prompt Comparison Type set to required blank matching, or treating a one-character space as blank are the three most common reasons a filter or condition rule silently drops the rows you expected.

## Match the Operator to the Field Type

Workday’s **Reference: Filter Operators** topic publishes the operator catalogs by field type. Memorize the emptiness pair that matches the field you are testing:

| Field Type | Emptiness Operators | Workday Description |
| --- | --- | --- |
| Text |  **is blank** / **is not blank** | Field value is empty / isn’t empty |
| Date |  **is blank** / **is not blank** | Field value is empty / isn’t empty |
| Boolean |  **is blank** / **is not blank** | Empty represents False; not blank represents True |
| Single Instance |  **is empty** / **is not empty** | Field value is blank / isn’t blank |
| Multi-Instance |  **is empty** / **is not empty** | Field value is blank / isn’t blank |

Currency and numeric fields do not get `is blank` in that reference table; compare them with equal to, not equal to, and the greater/less family instead. True/False Condition calculated fields and many condition-rule grids reuse the same field-type operator pattern: the Operator prompt only offers what the selected Field supports.

Fails

```
# Wrong emptiness operator for an instance field (operator will not behave like text blank)
Field:     Location (Single Instance)
Operator:  is blank
# Use is empty for single-instance / multi-instance fields
```

Works

```
Field:     Location (Single Instance)
Operator:  is empty
Comparison Type: Value specified in this filter
```

## Optional Prompts: Blank Prompt vs Ignore-If-Blank

Workday Education’s filtering chapter draws a sharp line between two Comparison Types that look similar in the filter grid:

| Comparison Type | Blank Prompt Behavior | Typical Intent |
| --- | --- | --- |
|  **Prompt the user for the value** | Workday still filters using the blank prompt value | Required criteria; empty means “match blanks” |
|  **Prompt the user for the value and ignore the filter condition if the value is blank** | Workday drops that filter condition when the prompt is empty | Optional criteria; empty means “do not restrict” |

If your optional Supervisory Organization prompt returns almost nothing when left empty, you almost certainly used the first Comparison Type. Rebuild the filter row with ignore-if-blank, re-run with the prompt cleared, and confirm the full population returns before testing a selected org.

For instance prompts that must treat an empty selection as “all values,” Workday’s filter-operator reference also documents an **And/Or** pattern: `in the selection list` paired with an **Or** row using **superset of the selection list** against the same prompt. An empty prompt then evaluates as True on the superset branch (equivalent to selecting all possible values).

## Instance Operators That Quietly Keep Blank Rows

Several single-instance and multi-instance operators treat blank values as a subset. That is intentional Workday logic, and it surprises authors who expect blank to fail every list comparison.

From Workday’s published single-instance examples:

| Field Value | Selection List | `in the selection list` | `subset of the selection list` |
| --- | --- | --- | --- |
| Chicago | Chicago Sacramento | True | True |
| (blank) | Chicago Sacramento | False | True |
| (blank) | (blank) | False | True |

So a filter of `Location subset of the selection list` against a prompted city list **keeps workers with blank Location**. If your business rule is “only workers with a Location in this list,” use **in the selection list** (or **any in the selection list** for multi-instance) and add a separate **is not empty** row when blanks must be excluded.

Related-business-object filters have a second trap documented in Workday Education: subfilters run before primary filters, and workers without related data can still appear unless the primary filter also requires the related object **is not empty**. That pattern is a frequent root cause of “my related amount filter did nothing” tickets. See [why a Workday report returns no rows](https://kiweely.com/guides/workday-report-no-rows) when the opposite problem appears.

## Spaces, Empty String, and Calculated Field Defaults

Filters that check **is blank** on text only match truly empty text. A calculated field whose default is a single space character fails `is blank` because the value contains one character. When an **Evaluate Expression** or similar text calculated field needs an empty fallback, use Workday’s Global **Empty String** field (or an equivalent empty Text Constant), not a typed space. Confirm with a diagnostic column that shows **Text Length** of the field: blank should be 0, a space is 1.

Boolean emptiness is another foot-gun. Prefer an explicit **equal to** False (Comparison Value check box cleared) when you mean False. Relying on **is blank** works for Workday’s documented Boolean blank-as-False behavior, but it confuses reviewers who expect blank and False to mean different things in other systems.

| Symptom | Cause | Fix |
| --- | --- | --- |
| Optional prompt empties the report | Comparison Type filters on blank | Use ignore-if-blank Comparison Type |
| Blank Locations still appear in a city filter | `subset of the selection list` treats blank as subset | Switch to `in the selection list` and/or add `is not empty` |
| Text “blank” filter misses rows | Field holds a space or placeholder | Default calculated text to Empty String; verify with Text Length |
| Related amount filter keeps workers with no expenses | Subfilter alone does not remove primaries without related rows | Add primary filter requiring related object `is not empty` |

## Prove the Filter in the Tenant

1.  Open the custom report **Filter** (and **Subfilter**) tabs; note Field type, Operator, and Comparison Type for every emptiness check.
2.  Run once with prompts cleared and once with values filled; compare row counts.
3.  Add temporary columns for the filtered fields plus Text Length or Count where helpful.
4.  Mirror the same operator choices in any **True/False Condition** calculated field or condition rule that is supposed to match the report logic ([condition rules that fail](https://kiweely.com/guides/condition-rule-not-working)).
5.  Re-test as a user without broad security if results vary by persona.

If you want the filter grid, prompt Comparison Types, and related-object emptiness checks reviewed against live report definitions in your tenant, [Kiweely Vine](https://kiweely.com/vine) can inspect those report filters and propose the corrected operators for your approval. Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month.

## Frequently asked questions

### Should I use is blank or is empty on a Worker Location field?

Use is empty or is not empty for single-instance and multi-instance fields such as Location. Use is blank or is not blank for text, date, and Boolean fields. The operator list on the filter row only shows operators valid for that field type.

### Why does leaving a report prompt empty return almost no rows?

If the filter Comparison Type is Prompt the user for the value, a blank prompt still applies the filter as a blank comparison. Switch to Prompt the user for the value and ignore the filter condition if the value is blank when an empty prompt should mean no restriction.

### Why does subset of the selection list keep blank instance rows?

Workday documents that blank field values are a subset of the comparison values. A blank Location therefore evaluates True for subset of the selection list against a city list, which is why many authors prefer in the selection list or is empty for instance filters.

### Does Boolean is blank mean the same thing as False?

For Boolean fields, Workday documents that is blank represents False and is not blank represents True. Prefer equal to with the Comparison Value check box cleared when you intentionally mean False rather than relying on blank semantics alone.

## Sources checked

-   [Reference: Filter Operators](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/set-up-reports/dan1370796447961.html)
-   [Sorting, Filtering, Prompting, and Totaling (Workday Education)](https://doc.workday.com/workday-education/en-us/course-manuals/workday-reporting/sorting-filtering-prompting-and-totaling.html)
-   [Evaluate Expression](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/calculated-field-functions/dan1370796323223.html)
-   [Configure Calculated Fields with True/False Condition](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/calculated-fields/calculated-field-functions/dan1370796333964.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Workday custom validations and condition rules: block bad data with Critical or Warning severity A Workday validation fires when its condition rule is true for invalid data. Critical blocks the step from exiting; Warning lets the user submit again. Maintain Step Conditions covers business processes, Maintain Custom Validations covers financials and payroll.](https://kiweely.com/guides/workday-custom-validations-condition-rules)
-   [### Why does a shared Workday report show blank columns or fewer rows to another user? Because sharing a report does not override report security. Each user sees results based on their own access to the data source, the data source filter and every report field, so one report can show blanks, zeros or fewer rows.](https://kiweely.com/guides/workday-custom-report-sharing-security-empty)
-   [### Why a Workday report returns no rows, or the wrong rows It’s rarely one cause. Test the data source alone first, then work through report filters, prompts, related objects, security and indexing in order.](https://kiweely.com/guides/workday-report-no-rows)
-   [### Why does my Workday calculated field return blank in a report? A calculated field returns blank when its function finds nothing to return, when its business object is not reachable from the report, or when the viewer cannot see a field it reads. Test one known instance first.](https://kiweely.com/guides/calculated-field-returns-blank)
-   [### My Workday business process condition rule is not working and the step did not fire: how to troubleshoot it Work through nine checks in order: the condition’s type and polarity, which definition ran, its effective date, the Rule Tester, the field values at that moment, rule logic, how the event started, step security, and parallel step order.](https://kiweely.com/guides/condition-rule-not-working)

### More guides on Reports and calculated fields

[All 25 guides](https://kiweely.com/guides#reporting)

-   [How to Fix CellLimitExceededException: Exceeded Cell Limit in Workday Custom Reports and EIBs](https://kiweely.com/guides/workday-report-cell-limit-exceeded-exception)
-   [How to Build Multi-Condition Evaluate Expression Calculated Fields in Workday Without Hitting Nesting Limits](https://kiweely.com/guides/workday-evaluate-expression-nested-calculated-fields)
-   [How to Build a Workday Payroll Summary Report by Worker and Earning Code Over Any Date Range](https://kiweely.com/guides/workday-payroll-aggregate-earnings-deductions-report)
-   [How to Build an Extract Single Instance (ESI) Calculated Field in Workday (With Examples)](https://kiweely.com/guides/workday-extract-single-instance-calculated-field)
-   [Workday Date Calculated Fields: Increment or Decrement Date and Date Difference](https://kiweely.com/guides/workday-calculated-field-date-difference-increment)
-   [How do I group, aggregate and drill down in Workday advanced, matrix and composite reports?](https://kiweely.com/guides/workday-matrix-reports-aggregations-drilldowns)
-   [Slow Workday Custom Reports: Fixing Data Source Filter and Calculated Field Timeouts](https://kiweely.com/guides/workday-slow-custom-report-performance-tuning)
-   [Workday Calculated Fields: How to Build Them and Fix Common Errors](https://kiweely.com/guides/workday-calculated-fields)

### From the blog on Reports and calculated fields

[All posts](https://kiweely.com/blog)

-   [How Consultants Catch Silent Report and Browser Regressions After a Workday Semiannual Release](https://kiweely.com/blog/regression-testing-workday-ui-and-timezone-changes)
-   [Why Deep Workday Calculated Field Chains Become Unmaintainable (and How to Audit Every Dependency)](https://kiweely.com/blog/auditing-deep-workday-calculated-field-chains)
-   [Kiweely builds a prompted Workday report, then answers from the tenant](https://kiweely.com/blog/workday-report-built-and-tenant-answer)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
