This is a migrated thread and some comments may be shown as answers.

Error when we have a lot of columns from datasource

2 Answers 52 Views
Grid
This is a migrated thread and some comments may be shown as answers.
Freddy
Top achievements
Rank 1
Freddy asked on 31 Jan 2018, 02:15 PM

Hi,

 

We have one grid in which we have one column for every day between two different dates, it works fine with one year but fails when we have more than one, you could see the error into this Dojo (https://dojo.telerik.com/asIVaS/2). It works with our previous version (2017R2SP1) but fails with newest ones. It looks like there are one error into rowtemplate. There is something wrong or any workaround to skip that error?

 

Thanks in advance

2 Answers, 1 is accepted

Sort by
0
Freddy
Top achievements
Rank 1
answered on 31 Jan 2018, 02:23 PM

Additional data:

 

Looks like works fine in Edge explorer, only fails in Chrome

0
Stefan
Telerik team
answered on 02 Feb 2018, 08:28 AM
Hello, Ainara,

Thank you for the provided example.

After additional research, this seems like the third Grid is hitting a browser specific as it has 500 columns. I tested it and it works and Chrome with 450 columns.

This was working before that the Grid rendering was changed a little bit in order to add more attributes for the accessibility and other functionalities which are making generated HTML larger.  

As this is a specific browser limitation, the Kendo UI team has no full control over it.

Please have in mind that 500 columns are a very large number and can cause different performance issues as well. Please try to reduce the number of column to an acceptable number in order to avoid the browser limitation.

Regards,
Stefan
Progress Telerik
Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
Tags
Grid
Asked by
Freddy
Top achievements
Rank 1
Answers by
Freddy
Top achievements
Rank 1
Stefan
Telerik team
Share this question
or