Skip to content

Troubleshoot a query that returns unexpected results

Per-attribute operator gaps

PRIZM Query's available condition operators are set per attribute, not globally across the whole module. One attribute on an entity can be missing an operator (most often "is null" / "is not null") even when other attributes on that same entity already have it.

Missing \"is null\"/\"is not null\" is a per-attribute gap, not a systemic PQ limitation

The Benefits History entity's Status attribute originally only exposed "is equal to," "is not equal to," and "is in list" — there was no way to query on Status being null/blank at all. JayStar added "is not in list," "is null," and "is not null" for that attribute (shipped r2.24). When reporting a similar gap, name the actual backing entity (e.g. "Benefits History"), not just the fund area you assume it lives under — the initial report on this ticket chased an HRA-specific angle before the real entity was identified. (IUOE-2702)

Data population vs. a stale saved query

"A field/filter shows nothing in PQ" has at least two very different root causes that look identical from the Result grid alone:

Rule out a data-migration timing issue before assuming PQ itself is broken

A field can be present and genuinely queryable in PQ while still showing as "not populated" because the underlying member data hadn't been migrated yet — a timing issue, not a PQ defect. The FedPAC/PEF "Date Card Signed" field traced to exactly this: confirmed populated correctly, in both PQ and Member Plus, once the later data migration ran. No code change was needed. (IUOE-1597)

A saved query can be built against the wrong field or value, not a data gap at all

A "Bad Addresses" saved query returned zero results because it filtered on the wrong field/value ("B" instead of the actual "Bad address" indicator) — not because the data wasn't there. The corrected query returned roughly 1,600 records once pointed at the right value. (IUOE-2351)

Before filing a new "PQ shows nothing" bug: cross-check the same field directly in Member Plus (or the equivalent record screen) for a few sample records to rule out the data-population explanation first, and double-check the exact field/value your condition is filtering on before assuming the data itself is missing.

Export and performance limits

The export row cap has already been raised once

A ~27,000-record query only exported 1,000 rows to Excel/CSV — a real platform-level cap, not a bug in how you built the query. This was addressed under JayStar ticket #292 and delivered in Sprint 5. (IUOE-1596)

A hang during Execute Query can cost your whole unsaved query build

A stuck "loading" state when running a report typically indicates the database is busy or a lost UI-to-database connection, per JayStar's own diagnostic framing — not necessarily a one-off fluke. Because Save/Load is the only persistence mechanism PQ has (see Reuse a saved query), save or export a complex query definition incrementally as you build it, rather than building a large query in one sitting, so a hang doesn't cost the whole session's work. (IUOE-2308)

Date format display quirk

A wrong-looking date picker format is a display setting, not a data error

PQ's calendar/date picker was previously showing dates in DD/MM/YY order instead of the expected US MM/DD/YY format — resolved as a display-format fix, not a data issue. If a date condition looks like it's filtering on the wrong day, check which date format the picker is actually using before assuming the underlying data is wrong. (IUOE-1593)

See Build and run a PRIZM Query for the query-builder mechanics these gotchas sit on top of, and Understand fund-sharded entities for the other major "silently returns nothing" trap — a query pointed at the wrong fund's backing entity.

Who can do this

Role Access
Super User View Only
Business Agent View Only
Management View Only
Membership Staff View Only
Accounting View Only
Contract View Only
H&W Staff View Only
ETF Staff View Only

All 8 roles have the same View Only access to Execute Queries, so every role runs into the same set of recurring "why doesn't this work the way I expect" situations — there's no role-specific variant of these gaps.

A PRIZM Query that returns nothing, hangs, or shows an odd value isn't automatically a bug. The patterns below are the recurring, already-diagnosed root causes behind real closed tickets — check these before filing a new one.