Skip to content

Build and run a PRIZM Query

Steps

  1. Sidebar > PRIZM QUERY opens the query builder: an Entities tree on the left, Columns and Conditions panels in the center, a Query Menu (New query / Clear Query / Load query / Save query / Execute Query) on the far right, and an empty Result panel across the bottom.
  2. In the Entities panel, expand the entity you need (Member, Employer, Contracts, and so on) and check the fields you want. Checking a field's checkbox is what actually builds the query — it populates both the Columns and Conditions panels with that field available to add.
  3. In Columns, click [Add new column] to add a checked field to the output grid. Repeat for every field you want displayed.
  4. In Conditions, click [Add new condition] under "Select records where all of the following apply" (an all/any toggle controls whether conditions are AND'd or OR'd together) and pick a field, an operator, and a value.
  5. Click Execute Query in the Query Menu. The Result panel fills in with a paginated grid (5 rows per page on-screen).

Things to watch out for

The UI label and the real field ID are often different strings

The query builder displays friendly labels with inserted underscores — "Work_Type", "Termination_Date" — but the actual Expr id values saved in the query's XML have no underscore: WorkType, TerminationDate. If you're hand-editing a saved query or comparing notes with someone else's query, check the real field id in the XML rather than guessing it from what the UI displays.

Expanding an entity is itself a live data dictionary

Expanding an entity node (e.g. Member) reveals its full field list — this is worth treating as a readable map of the underlying PRIZM data model, not just a UI panel. It's the fastest way to confirm a real field name exists (and what it's actually called) before you build a condition around it — e.g. confirming "SSN" vs "SSNx" as the two distinct Member SSN fields.

The Entities tree is virtualized and can be slow or jumpy on a long expanded entity

Some entities have more fields than fit the visible panel, so you'll need to scroll the panel's own internal scrollbar (not the page) to reach fields further down the list. The "Employer Plus" entity, for example, sits far enough down the top-level Entities list — after "Member Plus," before "Member Payment" — that it's easy to miss if you stop scrolling too soon.

Use the Result grid's own export button, not the Query Menu's Export links

The Query Menu panel has its own "Export to PDF/Excel/CSV" links, but these are permanently disabled in this environment — they never become clickable, even right after a successful execute. The working export path is the Result grid's own toolbar buttons ("Export to CSV" / "Export to Excel", Kendo grid controls) directly above the result table. These download the full, un-paginated result set in one click, even though the on-screen grid only shows 5 rows per page at a time — the fast path to analyze a whole result with local tools (awk, Excel, etc.) instead of paging through the UI by hand.

Aggregate columns exist but true GROUP BY does not work the way SQL would suggest

A small Σ icon on a column row (easy to miss) adds an aggregate column — known functions so far are COUNT and CNTDST (distinct count). But adding a Count aggregate alongside plain columns does not group rows by those plain columns the way SQL GROUP BY would; every row still shows a per-row count. See Reuse a saved query for a documented workaround (sort a distinct-count column descending) when you need something like "members with 2+ of something."

See Reuse a saved query for Load/Save mechanics and ready-made examples, and Understand fund-sharded entities before building any query that touches the Employer Plus 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 get identical View Only access to Execute Queries — PRIZM Query is a pure read/reporting tool, so "View Only" here doesn't mean a restricted preview the way it might on a data-entry screen; it means the entire module, for everyone, never writes back to underlying data. Building a query is really assembling an ad-hoc SELECT statement through a visual UI: you choose which tables (entities) to pull from, which columns to display, and which rows to filter to, then run it and read (or export) the result grid.