How do we aggregate multiple query returns for effective reports and labels? Example - I want to print a locality report on a single page that includes all of the citations to that locality. I build a locality query to build my locality report, but the result is separate results for each citation. Likewise for multiple collectors at a single field site or specimen.
Every row returned by a query corresponds to a new detail band in a report or label. If your Locality query returns multiple rows, it indicates that a one-to-many relationship is present, multiple values are returned, and it is not aggregated.
To get one row per record or locality, aggregate the related records instead of returning them as separate rows. In the query builder, select the relationship field that is aggregated (for example, Locality → Locality Citation or Collecting Event → Collectors), and use the table aggregation so the related records are combined into a single text string.
You can customize the aggregation’s separator, sort field, limit, and table format to control how the items appear in query results, reports, and/or labels (see Editing Table Formats and Aggregations). This keeps the report at one row per locality while still displaying all citations or collectors in a single, readable line. The limitation is that you cannot pull out individual fields into new column values in the query results to be shown independently on the label or report.