^{Originally posted by bhumikaguptaa September 22, 2025}
Description of issue

When a query is constructed to display output fields from different paths that share the same name (e.g., FullName), the query results grid displays incorrect data and uses ambiguous, non-unique column headers. The grid appears to populate all columns with the same name using the data from the first column encountered, rather than the data from their respective paths.

This causes two major issues:

• The data presented in the results is factually incorrect.
• The user cannot distinguish between the columns due to the identical headers.

Example Use Case
A user queries a Collection Object record where:
The determination taxon is Mesocestoides lineatus.
The host taxon is Vulpes vulpes.

Expected Behavior

The results grid should display two distinct columns with unique, descriptive headers and the correct corresponding data. For instance:
Column 1 Header: Determinations: Species - Full name | Data: lineatus
Column 2 Header: Host taxon: Species - Full name | Data: vulpes

Actual Behavior

The results grid displays two columns with identical headers, and both show the data from the first path.
Column 1 Header: Species - Full name | Data: lineatus
Column 2 Header: Species - Full name | Data: lineatus (This is incorrect)

Solution

The system should generate unique column aliases for the results view, perhaps by prepending a parent table or a portion of the field path to the column header. This would resolve both the data mapping error and the user-facing ambiguity.

Reported by

Alexis Beck, Le Muséum d’histoire naturelle de Genève
Link to the Bold desk ticket: https://specifysoftware.bolddesk.com/agent/tickets/197