Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[ui5-analytical-table]: When grouping by column A, the grouped row has an incorrect aggregated value in the grouped column

Cerrado
  • ¿Algo no está bien?
#8,060 6 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@plamenivanov91 ya está trabajando en esto.

Desde el 29/12/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

Bug Description

I have a ui5-analytical-table where it is possible to group by columns, even creating a combination of grouped columns. In such a table, in one of our scenarios, the value of column C, depends on the value of column B.
Both columns B and C have overwritten the event "aggregate".

Given I grouped the analytical table by columns A
When I group the table by column B
Then, the grouped row (where the value of the grouped columns is not shown) aggregates column B by selecting the first value, not triggering the aggregation events.

Example:
In the table in the image, I have the following aggregations:

  • Min Status column: returns a single status, returns "In Progress" if at least one row in the grouped rows contains this status. Returns "Finished" if all grouped rows are finished.
  • Job Due Date: returns the min date of the grouped rows. If Min Status column = Finished, then show "Finished"
Image

As you can see in the expanded grouping, Job Due Date = "Finished", despite having "In Progress" rows in its group. It happens because in the grouped row, props.cell.values = 'Finished'. This value is not the result of the aggregation events described above, but simply the selection of the first Min Status value.

Affected Component

ui5-analytical-table

Expected Behaviour

The grouped row should respect what is defined in the aggregation, even not showing the value in the cell.

Isolated Example

No response

Steps to Reproduce

...

Log Output, Stack Trace or Screenshots

No response

Priority

Medium

UI5 Web Components Version

2.17.1

Browser

Chrome

Operating System

No response

Additional Context

No response

Organization

No response

Declaration
  • I’m not disclosing any internal or sensitive information.
Lenguaje dominante
TypeScript
Estrellas
541
Forks
114
Merge medio
21 h 40 min
PR fusionados (30 d)
87

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de UI5/webcomponents-react

Todos los issues de UI5/webcomponents-react

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.