Troubleshoot a report that looks wrong¶
Stray punctuation when an optional name field is blank¶
Conditional separators need to vanish along with the blank field, not just the field itself
The Unpaid Buckets Report showed a dangling trailing comma for members with no middle initial — e.g. "Leon, Ricardo,". Two release-note mixups (a transposed tracker number, then an incomplete first fix under R2.16) delayed the real fix, which shipped in PRIZM 2.18 by removing the first-name/middle-initial comma entirely rather than conditionally suppressing it. (IUOE-2309)
Member-name formatting bugs cluster around "what happens when an optional name component is blank" — middle initial, suffix, and similar — and this pattern has kept resurfacing across different reports, not just this one. A missing comma between Last Name and First Name on the H&W Invoice Detail report, and a possibly-related Business Agent field rendering gap on the Member Detail Report, are both tracked as part of the same name-formatting family in this project's history, though neither has been confirmed against the same root mechanism as the Unpaid Buckets fix above. If a report shows a stray comma, missing separator, or oddly placed punctuation around a name, check whether the underlying field (middle initial, suffix, a business-agent assignment) is simply blank for that record before assuming the report's formatting logic itself is broken.
The general troubleshooting mindset for this module¶
Across the clusters documented on this section's other pages, the same shape of explanation keeps recurring: the report is doing exactly what it was built to do, and the apparent bug is actually one of these mechanisms underneath it.
- A field genuinely is blank, and the template didn't account for that — the name-formatting pattern above.
- The report's inclusion rule is narrower (or different) than it looks — e.g. the Paid Invoice Discrepancy report only compares invoiced amount to the Dues-allocated portion of a payment, not the full payment including overage (see Accounting's Reconcile an invoice discrepancy report), or Friendly & Final Letters running on PTD rather than balance-due (see Run a dues delinquency or Assessment report).
- A data or config condition upstream, not the report, is the real cause — multiple work records, a COBRA record mixed in, an incompletely migrated dues-rate record, or a trade-code mapping error, all covered on Run a dues delinquency or Assessment report.
- A report that technically "exists" doesn't cover the real front-line use case — the Member Delinquency report's bulk-only scope versus a single member's real-time status, which became a Change Order rather than a bug fix (same page as above).
- The report's own widget mechanics produced a silently blank or hung result — the checkbox-picker, period-dropdown, and render-timing quirks on Navigate the Reports catalog and avoid parameter gotchas.
Before escalating a "this report is wrong" finding, it's worth asking which of these five shapes the symptom actually matches — most of this module's ticket history resolves to one of them rather than a genuine new defect.
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 |
Every role shares the same View Only access to Reports (with the H&W category's fund-gating covered separately — see Run an H&W or compliance report). Because nobody can edit a report's output directly, "this report looks wrong" always means tracing the output back to a mechanism elsewhere in the system — this page is for whoever is doing that tracing, regardless of role.
This page pulls together a mindset that recurs across almost every cluster covered on the other goal pages in this section: a report result that looks like an obvious bug is, more often than not in this project's history, a real mechanism working as designed, a data condition the report is faithfully reflecting, or a cosmetic rendering gap — not a calculation error. Knowing the mechanism saves a round trip of filing (and then closing) a ticket that turns out to be expected behavior.