Welcome to the Angular feedback portal. We’re happy you’re here! If you have feedback on how to improve the Angular, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

Our use-case: 
Load a large dataset with many columns, display only a few columns but allow the user to customize which columns are shown in the table. 
We then use a per row quick view to show the entire row's data. 

Our data is modeled after Elasticsearch's ECS, so we have >1000 fields that are assigned to "[columns]". The problem is that even if 4 columns are marked as visible, the grid takes more than 4 seconds to load. 
If we only only assign those 4 columns to "[columns]" then it loads near instantaneous. But now the columns chooser is useless.

There is something about this that is unnecessarily inefficient.

I've replicated it here and logged when the server request finishes and when the dataBound event is triggered: 

https://stackblitz.com/edit/angular-infine-scroll-custombinding-gz5qfk

Load the page, and scroll down to load more data.

Empty



If you increase the columns to >2000, then the data binding takes more than 10 seconds.