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 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.
In your article: http://www.telerik.com/forums/how-to-make-a-non-editable-column-field, many developers make the point that the read-only attribute of a column should be part of the view, not model/data. By not providing a column property to prevent editing, you have put the view logic in the wrong place. Solution: Create a read-only property to each column to prevent editing.
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.
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).
Hello, from our development I could collect some suggestions for improvement, which we would be pleased about in the future: MVC -> Grid -> Export to Excel - Do not show columns in export - currently only possible with Javascript - Display additional columns in the export that are only displayed in the export and not in the interface
Thus avoiding the need to work around the timing problem with a timeout like this: columnReorder: function(e) { setTimeout(function() { // save data logic implementation. }, 100); }
I want to have checkboxes in group header as shown in the below example.
https://dojo.telerik.com/eKUzITAH/41
Once I click on the group header checkbox, the child group headers under the clicked group header and the data rows inside it should get checked and when it is unchecked all the datarows under the group header should get unchecked.
Individually if I check and uncheck a checkbox in the datarow,the parent group header should get checked if all the datarows are checked and should get unchecked if any of the data is unchecked under that group header.
The grid popup editor is great but when you have a large number of fields to edit the height of the popup window becomes impractical. What would work much better would be to split the single column of fields into two or more columns making the window wider but shorter and ultimately more manageable. Maybe the popup could have a "columns" configuration option to allow for this type of functionality.
Bug report
When the horizontal scroll of the grid is shown and is configured for RTL, the resize handle is mispositioned.
Reproduction of the problem
1. Make the grid scrollable and set explicit widths to all columns.
2. Make the grid RTL.
3. Introduce multi-column headers.
4. Notice that the columns cannot be resized due to the disposition of the handler.
5. Dojo for replication:
https://dojo.telerik.com/IZInOVUd
6. Notice that whenever the horizontal scroll is not present, the resize handle is positioned correctly.
Environment
* **Kendo UI version:** 2019.3.1023
* **jQuery version:** 1.12.4
* **Browser:** [all]
It would be nice to have the option to configure different column titles for the column menu. For example, when there is a multi-header Grid, you could use this functionality to add the header title to the column title. https://www.screencast.com/t/qgeK9fFMPP https://www.screencast.com/t/NRl61JFzFH
The Pager breaks if you use the setOptions method to alter its options.
Regression introduced with 2023.2.829
After checking a checkbox, only the arrows remain from the Pager.
The Pager should remain whole when you alter its options.
In addition to columns.minScreenWidth, the grid also needs columns.maxScreenWidth for the situation described here: "http://www.telerik.com/forums/need-columns-maxscreenwidth-too!"
Updating a single row by default expands ALL collapsed groups. Removing a single row or inserting a single row does the same. This design lacks granularity: an isolated change to a single row should not cause the expanded/collapsed state of all groups to change. If the user is focusing on flu cases in New York City and a new flu case is added to the Los Angeles group, why should every group in the grid be expanded? Only the group affected by the change should change its UI state. The grid should listen for the change event of the observed *row* and if it is felt that a change to the row's data should cause a UI change, only the group to which that row belongs should be changed.
It would be nice if its possible to slide threw the pages in a grid by using a slider in the footer.
The Grid already has beforeEdit event that can be used for preventing the editing depending on custom logic. The same thing could be used for preventing add or delete based on custom logic or validation.
Highlight a row during mouse over has to be done through CSS. However it doesn't work properly when there is a locked column, as there are two separate tables. This requires some programming. I suggest you embed it in Kendo, so we could easily use this feature without having to implement it ourselves.
The existing configuration(filterable.extra), can only support 1 or 2 input from the UI. It would be great if multiple filter criterion input from the grid UI will be supported in the coming releases.
I know it is possible to show/hide columns through the column menu, but there is something odd about being able to hide one column from another column's menu. Alternative is to implement something yourself and use the API to show/hide a column, this seems like something that should be an option in the grid. I am imagining a column chooser button (perhaps in the top left header) that opens up a list of checkboxes similar to what you see in the column menu.