I have a Kendo UI for MVC batch edit grid that will not update to the server once I have about 40+ rows of data being updated. I can update each of the rows individually or several at a time but once I have more than about 40 rows, it error somewhere in the jquery.1.7.2.js script. I have verified that the data I am using is not the issue. I have a ticket with Kendo but they say there is no such limitation. There are 13 columns but I am only updating 6 of them, I have hard coded the data in most of the string columns to "test" to try and minimize the amount of data.
Is there anyone who has a batch edit grid and can update more than say 50 rows at the same time?
Resolved. It was not the number of rows, rater the number of key pairs. The default is set to 1000 to stop Denial of Service attacks. Here is a link to an article from MS explaining the issue. MS Article
In short, here is the setting in the web config file, I bumpped the value to 10,000 and stopped getting the error.
<configuration>
<appSettings>
<add key="aspnet:MaxHttpCollectionKeys" value="10000" />
</appSettings>
</configuration>
Related
I have a grid with a big set of records(round 10,000 on an average). I have implemented server side paging on the grid to retrieve 50 records at a time. Everything with the grid is working perfectly fine till I decide to do a export to pdf from the grid.
When I try to do the same the export takes round 5-6 mins on an average to complete. I tried to debug on the server side and realised that multiple calls to the server were being made to retrieve the data for the export which probably was eating up the time. I alternatively tried to modify the set of records retrieved to 1000 at a time so as to reduce the server calls to eventually reduce the time taken for the export. But now while trying to export to pdf the page crashes. I changed the set of records to 500 but the crash still happens when exporting.
On another note the export to excel works pretty fast in round ~4 secs. When trying to debug I found out that there was only a single call to the server made while exporting to excel and this renders the entire set of data as well.
Please note that I am using the kendo defaults for exporting to pdf and excel with the grid.
Thanks.
you need implement server side export.
kendo says :
Important
When the allPages option is set to true and serverPaging is enabled, the Grid will make a "read" request for all data. If the data items are too many, the browser may become unresponsive. Consider implementing server-side export for such cases.
look this page
Full example : link
I am facing the problem with jqgrid pagination.
I have a json objects in client side cache (in javascript object).
My jqgrid data type is local.
I cannot set the whole cache to jqgrid.
Let say in cache 1000 records, and on first load, I wants to provide 10 records only and when user press next button, I will read the next 10 records from cache and populate the jqgrid.
But when I set data type local and provide the 10 records on first load then jqgrid pagination show 1-10 of 10 only (instead of 1-10 of 1000).
Can you please help me to solve this problem.
Thanks & Regards,
Brijesh Baser
I am using kendoUi Grid with 20k records, When i am changing page size 20 to 200 grid taking 40 to 50 sec to work. some times it taking min. paging is client side only.
For large datasets, it's better to use server paging, mainly because:
Faster loads
Avoid wasting memory
Avoid unnecessary database and network loads, database just gives you the number of records of the current page
You should consider enabling server paging at datasource level, and then read pagination values on backend side before performing the query to the database.
http://docs.telerik.com/kendo-ui/api/javascript/data/datasource#configuration-serverPaging
good question, i am also faced this type of issue.
Please use MVVM logic instance of MVC for bind the grid,
for more please find this below link.
http://demos.telerik.com/kendo-ui/grid/mvvm
I am using Mojarra 2.1.19. I have a simple Facelet which contains only one table with 500 rows and 12 columns. The cells contain only text property data. It needs about 2 seconds to execute the render response phase.
As a result the application is not very responsive. Also all rows must be seen. The client doesn't want pagination.
Any suggestions? Is Mojarra really so slow?
I apologize, there was JSF debug logging turned on, and it made the execution slower. I turned off the logging and the simple table is fast now.
I'm working on a project where I have to fetch data from a database then present results in tables with at least 200 rows until 3000 rows.
I tried first Pagedlist and noticed that only the fixed number of records per page is displayed in the client side and each time when the user change the page, there is a new request to the server.
For tablesorter, I noticed that all the results are displayed and paging is only visual (only the presentation of table) but everything is in the client side
Is my understanding correct?
What I want to know is which approach is better (in time execution)?
Actually I'm working on localhost and there is only me as user so I can't notice the difference even tablesorter take more time to load in the first time but after it's very quick meanwhile the pagedlist method is faster in loading page but each time it request the server to change page and load the according data
When finished the application will be in the server and many users will have access to the application to add, search delete...
Which of these two approaches is a better choice?
Thanks