Is it possible to filter based on an empty field?

[SimonJ473792863]

I've successfully used boolean core UI filters in the past to include/exclude records that have empty fields however now that I have started developing dashboards in PA experience I cannot find the equivalent functionality. True/False filters look the closest but do not seem to validate on empyy/non-empty fields.

I don't believe it's possible to include core UI filters in PA experience dashboards, is this feature available via a different mechanism? 

[Naveen20]

In the classic reporting/list view, you can use conditions like field is empty or field is not empty, but PA experience dashboards handle filtering differently. Here's what's going on and your options:

Why True/False filters don't work for this: True/False interactive filters in PA are designed strictly for boolean (true/false) fields. They evaluate the field's actual boolean value, not whether a field is populated or not.

How to achieve empty/non-empty filtering in PA dashboards:

There are a few approaches depending on your use case:

1. Indicator-level source conditions — The most reliable method. Edit the PA indicator definition itself and add a condition on the "Source" tab using field is empty or field is not empty. You can create separate indicators for "with value" and "without value" scenarios if you need both views. This works because the indicator source condition builder uses the full GlideRecord condition engine, not the PA interactive filter framework.

2. PA Filter records (sys_pa_filter) — Create a predefined PA filter with the empty/non-empty condition baked in. These can then be applied to widgets within the PA dashboard. The PA filter condition builder typically supports more operators than the interactive filter UI exposes.

3. Breakdown with "Empty" element — If you're using a breakdown on the field in question, PA will often surface an "(empty)" element in the breakdown results, which you can then use to include/exclude via breakdown element filtering.

4. Calculated field / boolean indicator source workaround — Add a calculated or derived boolean field to the source table (via business rule or calculated field) that flags true when the target field is empty. Then your True/False interactive filter would work as expected against that derived field.

Regarding core UI filters in PA dashboards: You're correct — core UI condition-style filters with the full operator set (is empty, is not empty, starts with, etc.) are not directly available as interactive filters in PA experience dashboards. The interactive filter types (Choice, Reference, True/False, Date, etc.) are a more constrained set.

If this is blocking you on a dashboard you're building, the indicator source condition approach (option 1) is usually the quickest path.