Query Results Show Incorrect Data and Ambiguous Headers for Fields with the Same Name

[bhumikaguptaa]

Discussed in #7435

^{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

[grantfitzsimmons]

From Alexis Beck at NHMG via email:

I just wanted to report you that I was hoping two important fixes would be included in the release.

Querying different taxon genus/species in the same query (eg. I want the current det + preferred taxon + host taxon). Only one of them is displayed in the query result

[specifysoftware]

This issue has been mentioned on Specify Community Forum. There might be relevant details there:

https://discourse.specifysoftware.org/t/chrono-strat-and-chrono-strat-end-returning-the-same-value-in-queries/2923/5

[grantfitzsimmons]

See that this was reported on the Speciforum by Michail at Museum of Geology and Paleontology, Athens

Chrono Strat and Chrono Strat End returning the same value in Queries

Hello, thanks for answering.I am on v7.11.1. I did edit the XML of the form to make Chrono Strat End appear (since it was hidden). I will post the XML View Definition at the end.

Currently we are on a testing stage of Specify 7, trying out various features and capabilities of the software in order to prepare soon a fully configured version for our institution.

One thing that we care about is ths DwC export, which requires distinct chronostatigraphic fields (Start-End) in the category of Geological Context ( https://dwc.tdwg.org/terms/#geologicalcontext )

For example, we have fossils whose age is determined as Pliocene-Pleistocene (earliestEpochOrLowestSeries - latestEpochOrHighestSeries) or Tortonian-Messinian (similar earliest-latest Stage/Age), thus require two fields to record this information.

To determine the earliest chronostatigraphic value we use the “Chrono Strat” field, and to determine the latest chronostatigraphic value we use “Chrono Strat End”

While preparing the query to export a test csv file, I fell on an interesting behavior. This can be showcased by the following screenshot, the query export itself and the csv file.

If I set the query for Chrono Strat/Chrono Strat End in “Collecting Information > Paleo Context > Chrono Strat/Chrono Strat End > any rank > Name”, it displays the correct values of the fields. However, if I instead set it into “Collecting Information > Paleo Context > Chrono Strat/Chrono Strat End > [Rank] > Name” and I choose a rank (ex. Age/Stage, Series/Epoch etc.), it only displays the value of the Chrono Strat field, for both Chrono Strat and Chrono Strat End!

Our goal is to export the full array of Chronostatigraphy (for both Earliest-Latest combinations) as displayed in the DwC Geological Context category

Thank you for attaching the screenshots and query definition–they were very helpful to us when trying to recreate the issue. This is indeed a bug, and it is caused by issue #7436 on GitHub, which causes the wrong data to be returned when two fields have the same heading in the query (in this case, Stage/Age). You will need to use the (any rank) > name field like you did at the top of the query to avoid the issue. Please let us know if you have any more questions!

[CarolineDenis]

Could be also related in part with #7449