I would like to see the grid allow the adding of a new row via the keyboard when batch editing. When the user is on the last row and last cell they can hit tab and the grid will add a new record and with focus on the first editable cell. Or the user can hit enter anywhere on the last row to create a new row. This would allow for rapid entry of several new rows of data. It would allow the user to key in data in a similar way a spreadsheet like Excel would behave.
This may be more of a bug, but Kendo does not allow you to call showColumn() or hideColumn() when the grid itself is not visible. If you look in the showColumn / hideColumn methods in kendo.grid.js, we can see that there is a .filter(":visible") on the columns in place. Unfortunately for us, our Kendo grid isn't always visible (it can be collapsed: think $.slideUp). Instead, we get an error saying (on the following line) that "style" could not be set on undefined - because our hidden grid's hidden column header doesn't pass the :visible filter. Thanks!
One should be able to cancel the detail expand or collapse events of the grids by providing a Expanding / Collapsing event. One use case for this that would be way easier to implement is when one is using a detail template to edit some form of data related to the expanded row but not bound to it's data item, instead bound to specific data coming from other source. If when you expand another row the previously expanded one gets collapsed I would like to be able to prevent that on those events to check for changes, challenge the user and act accordingly.
Currently the grid only includes row virtualization. Column virtualization would be really beneficial for projects that display many columns
Hi Team,
I would like to request the functionality to sort the MultiCheck Filter for the Kendo UI Grid. For example, maybe adding a columns.filterable.sort property.
Thank you!
The grid "beforeEdit" event is designed, as per documentation, "for preventing the editing depending on custom logic". However, this event provides only information about the edited row, not cell, which severely limits what that logic can do. A related event, "edit", passes information about the container, which is a table cell in incell mode. There is no reason for "beforeEdit" not to do the same - both event are triggered merely several lines apart.
Enable on-the-fly changes of selectable (selection mode) in the Grid widget
there are ready to use methods fadeIn & fadeOut for animation In jQuery. Kendo UI Window already uses nifty close-effect, how about implementing this behavior for a grid-control. Expanding/Colapsing Detail-Gird in Hierarchy will go smoothly and comply with other controls' animation.
While it is currently possible to do this in JavaScript, it would be nice to have the functionality integrated into the Grid filter row. For example, columns.Bound(c => c.Title).Title("Title") .HeaderHtmlAttributes(new { style = "text-align: center;" }) .Filterable(f => f.Cell(fc => fc .ShowOperators(false) .Operator("Contains") .Template("fnFilterAsYouType") .Placeholder("Title") ));
Frozen Columns is a really useful addition to the grid, but we're not able to implement it at present as we don't want to force our users to always have one column locked. We don't want to dictate which column that should be, e.g. fixing the LH column. If we could enable Frozen Columns giving the user freedom to freeze one or more columns of their choice, that would be ideal.
The loading indicator is not showing when the height property of a grid is not set.
The above behavior has been requested several times in the following forum thread.
https://www.telerik.com/forums/grid-column-locking-with-detail-template
I would like for this limitation to be revised or for some other solution to be provided.
<pre> Kendoui grid date filterable "Is equal to" - Make it have a range base on what is input If you have a date column in a grid and you filter it and select "Is equal to" it currently doesn't work very good unless your dates/time are all on 12:00:00.000 AM Maybe you could make the filter do this when "Is equal to" If you select or inputput: 2/22/2004 It will find the following rows: 02/22/2004 00:00:00.000 <= datesFound < 02/23/2004 00:00:00.000 2/22/2004 06: It will find the following rows: 02/22/2004 06:00:00.000 <= datesFound < 02/23/2004 07:00:00.000 2/22/2004 06:50 It will find the following rows: 02/22/2004 06:50:00.000 <= datesFound < 02/23/2004 07:51:00.000 2/22/2004 06:50:20 It will find the following rows: 02/22/2004 06:50:20.000 <= datesFound < 02/23/2004 07:51:21.000 2/22/2004 06:50:20.034 It will find the following rows: 02/22/2004 06:50:20.034 <= datesFound < 02/23/2004 07:51:21.035 Maybe have a toggle for (0-12 AM/PM) or (00-23 24 hour clock) in the datetimepicker with a default setting that can be configured. Maybe make the datetimepicker have a range for each Hour, minute, second, millisecond, AM/PM * or blank - could act like a regular expression but would need to have the higher unit set. IE: ( 06:50:20.035 , 06:50:20.* , 06:50:*.* , 06:*:*.* , *:*:*.* or 6:50:20.035 AM, 6:50:20.* AM, 6:50:*.* AM, 6:*:*.* AM, *:*:*.* * Not this: *:50:*.* * ). HH , MM , ss , fff 00-23;*, 0-59;*, 0-59;*, 000 - 999;* or H , tt , MM , ss , fff 0-12;* , AM/PM;*, 0-59;*, 0-59;*, 000 - 999;* The yyyy,MM,dd could also be done this way so you could get all the rows for a yyyy****, yyyyMM**, yyyyMMdd </pre>
When performing a grid refresh, the grid re-renders the all the grid rows. I think it would be very efficient to have a choice to render specific, changed rows. This is valuable if the grid has many items (200 items for example).
For performance reasons, we would like to only show the group headers collapsed when first grouping, and only add its child rows when expanded. This is done for hierarchical grids and minimizes unnecessarily large DOMs for data the user will never look at.
Currently yo keep the selected row after refresh one needs to store the data first and then loop through all the rows to find it and select it again. This is because the uid changes after refresh. This does not work very well with large number of rows. It would be great to have a setting that allowed the selected rows or cells to be kept after the refresh.
On updating the dataItem of a master row using the Observable "set()", the master row will repaint itself. However it also collapses the expanded detail row. The detail row can be expanded programmatically but this is clunky: the detail row flashes briefly while it collapses then immediately re-expands The default behaviour should be to leave the row expanded.
I like what FooTable.js does with a html table. (hide fields based on breakpoints) and place them so that they are available via click on +
The grid editable confirmation(delete alert) only popup jQuery alert currently, I want custom the dialog box style with window widget~