Skip to content

Troubleshoot common Employer data issues

Things to watch out for

A multi-fund user seeing a field group repeated several times is seeing one row per fund, not a rendering bug

Employer+ shows per-fund-duplicated field groups (like the four Invoice Preference fields) for a Super User with access to multiple funds, stacked with no header distinguishing which fund each group belongs to. That duplication is correct by design per BLR 7.2.5.1.4 — the missing per-group fund header was the actual gap, and it shipped a fix in Sprint 3. If a field looks repeated with no labels, check whether it's one row per fund before assuming the UI is double-rendering. See Configure Employer+ invoicing settings for the full Employer+ field reference. (IUOE-1530)

Employer Details not loading its State dropdown value was a repeatable, already-tracked display bug

This was confirmed repeatable across multiple employers and search paths and tracked internally as JayStar #327, not an isolated one-off. If a State value looks missing on Details after loading a record, that's a recognized historical pattern rather than something new to diagnose from scratch. (IUOE-1585)

Printed Employer Profile punctuation oddities (stray commas) were a cosmetic fix, already resolved

The printed Employer Profile previously showed stray commas around contact names; this was fixed. If you see similarly malformed punctuation on a printed profile again, treat it as a new, distinct report-formatting issue rather than a recurrence of the same ticket. (IUOE-2042)

A field that looks required but is sourced elsewhere can have the requirement safely removed

Employer was previously required when entering COPE/PAC pledges, even though the employer relationship for a pledge is already derived from the member's work record — making the Employer field on that screen redundant, not load-bearing. The requirement was removed. This is a useful general pattern for any other data-entry screen where a field "looks required" but its value is really sourced from a related record elsewhere in the system — worth checking before assuming a similar over-strict required-field complaint needs a new workaround rather than a requirement correction. (IUOE-2517)

The static bar's Employer label is cosmetic — it reflects the last Employer record saved, not dues-rate source of truth

For a member with more than one active work record, the static bar's Employer field just shows whichever Employer record was saved most recently — JayStar confirmed that showing "Multiple" there wasn't considered a defect, because Dues Rate is Jobsite/Contract-driven, not Employer-driven. The rate-selection bug itself (which work record's rate displayed) was real and was fixed. The business rule that governs which rate displays/assesses when a member holds multiple active work records: prefer the sole full-time (FT) record if there is one; if multiple FT records exist, prefer the oldest open one. Teach this rule directly rather than treating each new "wrong employer/rate shown on a multi-job member" report as a fresh bug. (IUOE-2486)

Related: Look up an employer and its records, Configure Employer+ invoicing settings, roles/contract/create-a-new-contract.md (for the Employer search/type-ahead and Employer-ID-assignment clusters).

Who can do this

Role Access
Super User Visible (read); Add/Update on Details per the module's own rules
Business Agent Visible (read)
Management Visible (read)
Membership Staff Visible (read); Add/Update on Details per the module's own rules
Accounting Visible (read)
Contract Visible (read); Add/Update on Details per the module's own rules
H&W Staff Visible (read)
ETF Staff Visible (read)

Recognizing these patterns is a reading/reasoning skill, not a permission — every role can view Employer records and hit the same oddities while looking something up, regardless of who can actually edit the Details tab. See Look up an employer and its records for the permission detail on editing.

This page is mostly fact, not procedure — it's the recurring mechanisms behind closed ClickUp cases on Employer Profile data entry/display, Employer field-requirement rules, and the member static bar on multi-jobsite/multi-employer members, grouped by root cause rather than by individual ticket. The goal is to teach the underlying mechanism once per cluster, since that's what you'll actually need to reason through when a similar-looking but new issue shows up. (Two other Employer clusters — search/type-ahead reliability and Employer record creation/ID assignment — are already covered on roles/contract/create-a-new-contract.md; this page doesn't repeat that detail.)