FK Columns Render Raw UUIDs In List Surfaces Instead

by Jule 53 views
FK Columns Render Raw UUIDs In List Surfaces Instead

When working in list views across the platform, every foreign key column - like those linking AssessmentEvent records to schools or departments - today displays the raw UUID instead of readable titles or names. For example, a teacher’s workspace might show a7b3c9d2... instead of ‘Oakwood Academy.’ This isn’t just awkward - it’s a productivity killer.

  • The problem: List surfaces render FK columns by default using UUIDs, not the human-readable titles or department names they represent.
  • Why it matters: Users can’t instantly recognize records in grids, forcing clicks through dozens of rows just to find one. This hurts admin workflows and data scanning.
  • Psychology: We expect clarity at a glance. Raw UUIDs break visual scanning habits built into list-based interfaces, triggering frustration and cognitive overload.

But here’s the good news: this is fixable without schema changes. By resolving FKs to the title or name field of the referenced entity - or its first str/text field - display surfaces can show meaningful names instantly.

  • Common resolution path: Use a runtime lookup to map UUID to display label, first applied at render time.
  • Works across 49 entities and 180+ list surfaces, from AssessmentEvent to StudentProfile.

FK columns rendering raw UUIDs isn’t just a quirk - it’s a silent barrier to efficient work. When did your last list surface feel more like a cryptic puzzle? The fix is simple: let names replace codes - where visibility meets usability.