When a custom table is added to a report through a join, the report currently shows the first available field by default instead of the field that best identifies the record.
This can feel inconsistent and confusing. Standard records usually default to a recognizable name field, but custom table records may show something less helpful, like an ID or % complete.
Makes reports difficult to read
Causes manual cleanup
Inconsistent experience between standard records and custom table records
Joined custom table records default to the table’s main display field — such as Name — when one exists. If there is no clear display field, the current fallback behavior could still apply.