Client side data from odata works great, filter and paging with no extra coding. Surely grouping should be done client side, requesting the amount of data it requries from the odata source. This can make sure when groups are closing, the javascript can request more data to fill up the paging.
Hi When using RadGrid with popup Edit forms, it would be great if we can have a property that allows users to position the edit form just above or below the row being edited (depending on available space). See attached file which contains three JS functions that we use to position our edit forms. We rely mainly on the '_radGridCenterPopUpToSelectedRow()' which positioned the edit form below the row being edited (or above if there is no space below) but this does not work right if the page has scrolled vertically or if we are in a child grid of an hierarchical grid. It would be great if this could be a standard property for the Edit forms so that we do not need to keep computing the position for the pop-up edit forms. Thanks S
The grid should provide an in-built option for the filtering to be initiated only on Enter key press and not on Tab or input blur.
Bind RadGrid client-side to a WCF Data Service, using a separate GetCount method. Then filter on column typing the value 12345 in the filter textbox. The result is that the value is not passed correctly to the web service.
I am new to telerik controls. My requirement is i should display "n" number of items based on values available in a xmldocument which is generated at runtime. is it possible to add the columns at aspx itself and bind it or it can be done only through dynamically creating datasource and binding it? Also i should show some images and checkboxx for selection based on some conditions
Having a RadGrid in batch mode with Master and Details tables, when you add a new master record, you are not able to add a new detail record until you save the master record. This feature should be built in the RadGrid.
Natural Sort-Option for RadGrid to sort the items in the grid in a natural way. By natural sort we mean sorting like StrCmpLogicalW (Win32 API).
Having Paging enabled, the Column Aggregates should be calculated based on the data from all of the group's items, even if the group is spread over several pages. Currently, only the data from the visible items on the current page are calculated.
This behaviour only occurs in Chrome Webbrowser if you select an item in the grid in the bottom area of a list which has of more than 20 elements. If you start to drag the item, it appears far to low which means that it is sometimes not on the page anymore. It is even possible to redo this with the telerik demo ( on http://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/rows/drag-and-drop/defaultcs.aspx) if you use the pager some times.