Skip to content

Understand fund-sharded entities

The core mental model: one entity, different funds, different backing tables

Some entities that look like a single Fund-selector-scoped view are actually split into separate backing database views per fund, with the entity tree showing the same friendly name ("Employer Plus") no matter which fund is selected. A query built while Fund=Union is pointed at one real table; the identical-looking tree entry under Fund=H&W is pointed at a different real table with different field ids. Switching the Fund selector does not make a Union-built query resolve against H&W data — it just runs the same query expression against a fund context where that expression's backing entity doesn't exist, which returns an empty result, not an error.

This matters because an empty result looks exactly like "there's no data" or "this is broken" — there's no on-screen signal that you're pointed at the wrong entity for your fund.

Confirmed example — the Employer Plus entity (the data behind the Employer Plus tab; see Configure Employer Plus invoicing settings for the screen this backs):

  • Under Fund = Union, the tree's "Employer Plus" entity is v_pq_shop_plus, with fields Shop_id, Number_Of_Buildings, Dues_Ded_Flag, PacDedFlag, Invoice_Delivery (real id InvoiceDelivery1), Invoice_Grouping, Invoice_Sort_Order, Invoice_Billing_Cycle.
  • Under Fund = H&W, the same tree entry is a different entity, v_pq_shop_plus_HW, with the same field set but without the Union variant's "1" suffix (InvoiceDelivery, InvoiceGrouping, and so on).
  • A v_pq_shop_plus_ETF almost certainly exists on the same pattern but hasn't been confirmed.
  • The plain Employer identity entity (vw_pq_tblShops_IUOE399 — EmployerID, EmployerName, etc.) is the exception: it is not fund-sharded, confirmed because both the Union-built and H&W-built Invoice Delivery queries successfully reference it.

The fix

Build or load the fund-specific query — don't switch the Fund selector against a query built for a different fund. If you need the same report for multiple funds, that means maintaining one query per fund (see employer-invoice-delivery-option.xml / -hw.xml and employer-invoice-sort-order.xml / -hw.xml in Reuse a saved query as paired examples of exactly this pattern), not one query you expect to "just work" after flipping the selector.

Things to watch out for

An empty result from a loaded query is not necessarily zero matching records

If you load a saved query, switch funds, re-execute, and get an empty Result grid, the default assumption should be "wrong fund context for this entity," not "no data exists." This was confirmed directly: re-running a Union-built query (v_pq_shop_plus.InvoiceDelivery1) after switching to Fund=H&W reliably returned an empty result set, which initially looked like a tooling bug but was actually the expression referencing an entity that simply doesn't resolve in that fund context.

Verifying a fund-specific entity means building live in that fund context, not guessing field ids

The H&W variant's field ids (InvoiceDelivery, InvoiceGrouping, InvoiceSortOrder, InvoiceBillingCycle, no "1" suffix) were confirmed by building a query live while Fund=H&W was selected and inspecting the resulting saved XML — not by assuming the Union naming pattern carries over. Do the same for any other fund-sharded entity you're not sure about before trusting a field id you haven't personally confirmed in that fund's context.

Not every entity is fund-sharded — don't over-apply this caution

The plain Employer identity entity (vw_pq_tblShops_IUOE399) works unchanged across funds. Treat fund-sharding as a per-entity fact to verify (by building live in each fund and comparing the saved XML), not a blanket rule that every entity needs a separate per-fund query.

See Build and run a PRIZM Query for general query-builder mechanics and Configure Employer Plus invoicing settings for the live screen this entity's data backs.

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 identical View Only access to Execute Queries, which means every role hits this same schema fact if they build a query against the wrong entity for their current fund — there's no role whose permissions shield them from it.