primeng p-table: RowGroup not grouping on subsequent pages

Describe the bug

We have a p-table component using [lazy]="true" and the following ng-templates:

<ng-template pTemplate="groupheader" let-rowData let-rowIndex="rowIndex" let-expanded="expanded">

<ng-template pTemplate="rowexpansion" let-rowData let-columns="columns">

We also have the row toggle as [pRowToggler]="rowData".

On the first page, it correctly groups by the groupheader / pRowToggler, but on all subsequent pages the grouping stops and each line is shown individually.

Page 1:

Page 2:

Environment

Angular 14.0.3 / PrimeNG 14.0.0 testing with Chrome.

Reproducer

https://stackblitz.com/edit/github-sb1bvu?file=src/app/app.component.ts

Angular version

14.0.3

PrimeNG version

14.0.0

Build / Runtime

TypeScript

Language

TypeScript

Node version (for AoT issues node --version)

16.13.1

Browser(s)

No response

Steps to reproduce the behavior

Lazy load data into a p-table component with a paginator
Click on any page other than page 1
Note that the grouping is no longer applied

In Stackblitz repo, click page 2, rows no longer grouped:

Expected behavior

p-table continues to group by the unique pRowToggler as defined in the groupheader, as it does on page 1.

Aug 11 '22 14:08 psarno

I also have that problem with lazy and rowGroupMode="subheader"

Demo https://stackblitz.com/edit/primeng-tablelazy-demo-udw8pv?file=src/app/app.component.html

Aug 23 '22 11:08 ariancruz

This is still causing us problems in production and I don't have a workaround.

Sep 21 '22 18:09 psarno

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you reopen the issue so we can include it in our roadmap? Please don't forget to add your feedback as a comment after reopening the issue. These will be taken into account by us and will contribute to the development of this feature. Thanks a lot for your understanding!

Best Regards,