Hello Claudio,

Thank you very much for the feedback provided.

The requested feature is still not part of our immediate development plans and we are still tracking the demand for it.

As of now, the suggested workaround of creating the multi-column headers dynamically based on a known number of levels is the way to go. Please, check out the replies of my colleagues Dimiter and Svetlin for further reference.

Here is an updated version of the provided StackBlitz demos:

https://stackblitz.com/edit/angular-bkdaqw

Regards,
Georgi
Progress Telerik

Hi Maitri,

Thank you for the feedback. At the moment we haven't added the requirement to our future development plans. We are still tracking the demand. For now the suggest approach of creating the multi-column headers dynamically based on a known number of levels is the way to go.

Regards,
Svetlin
Progress Telerik

Hi Jason,

What could be done at this point is to create the multi-column headers dynamically but based on a known number of levels as demonstrated in the suggested example. I am pasting it here for reference:

https://stackblitz.com/edit/angular-tpdqhq-kyled3?file=app/app.component.ts

Regards,
Svetlin
Progress Telerik

Hi Jason,

We keep tracking the customer demand for this enhancement. Up to now, the requested feature is not added to our development plans, but the workaround that my colleague shared is still valid. Based on custom logic the desired multi-column headers can be achieved by iterating column configuration objects with *ngFor Angular directive. Please check the StackBlitz example in the Dimiter's reply for more details.

Regards,
Martin
Progress Telerik

Hi Zaw,

The feature in question is not available yet, but we are tracking this feature request, and will consider it based on the customer demand. Meanwhile, you can implement a custom solution, based on a previously known levels of nesting, e.g.:

https://stackblitz.com/edit/angular-tpdqhq-kyled3?file=app/app.component.ts

The solution is not applicable for dynamically creating the required markup for unknown data structures or when the levels of nesting are not known in advance, but is applicable for most practical purposes as real-world scenarios rarely involve indefinite levels of nested data.

Regards,
Dimiter Topalov
Progress Telerik