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.
Kendo grid doesn't have in-built functionality to prevent row selection based on some condition. One way is to remove css class "k-state-selected". But i think there should be something like "changing" event which will be called before "change" event. In that event developer write code and can cancel "change" event. Or Boolean property something like "enabled" at row level (or cell level for cell selection) .
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.
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.
It would be nice to have the option for a single filter input that searches all columns on the Grid. I was able to implement my own custom solution but having to apply that to every grid in my app is cumbersome. I understand the importance for the flexibility side of having each column with its own filter box, but for simpler apps this is overkill and a single filter box is enough. The column component already has the [filterable] flag so this can possibly be used to exclude any columns if necessary. I was thinking of something similar to what is an out of the box feature for the Datatables JS plugin https://datatables.net/ Default search box that searches everything. Very simple to use and understand for basic users or when your application only calls for something that simplistic.
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.
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]
New items (rows) are not shown in grid when they don't match the filter settings made to the grid. So it would be really useful if applied filters and sortings were resetted when new items are created.
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.
It would be nice if its possible to slide threw the pages in a grid by using a slider in the footer.
In the JQuery Grid if you have the following column definition (for example): [ { "field": "Name", "title": "Name" }, { "title": "Address", "columns": [ { "field": "Street", "title": "Number & Street" }, { "field": "City", "title": "City" }, { "field": "PostCode", "title": "Post Code" } ] }, { "title": "Contact Details", "columns": [ { "field": "Email", "title": "Email Address" }, { "field": "Phone", "title": "Phone Number" } ] }, { "field": "DOB", "title": "Date of Birth" } ] When you drag the multi-column header "Address" and drop it over "Date of Birth" the header and it's child columns move as expected but the column headers in the two multi-columns get mixed up. This only seems to happen when dragging a multi-column past another multi-column in either direction.
Currently the new select column and the "selectable" setting of the grid are mutually exclusive. This seems completly counter intutive. If you you have a select column and the "selectable" mode set to "multiple", then when you drag select or ctrl click on row the checkbox to be selected. Right now it's not.
Currently the only way to make column headers fixed and always visible as you scroll through a Kendo Grid is to make the height of the grid fixed. This doesn't allow responsive UI and dynamic sizing of the grid. I would like to see support for having fixed headers regardless of height of the grid, such that the grid may fill whatever container it's in and change size while allowing this.
This Telerik response confirms the current functionality:
https://www.telerik.com/forums/columns-header-always-on-top
Please add a simple way to add column calculations to the grid. From simple addition and multiplication to complex calculations across grid columns. Key features would include: Calculations fire on key up key down events for selected cells Formula builder like excel Calculated fields automatically save to db on save Calculated fields included in aggregates in footer Thanks!
I do not understand the rational behind this behaviour other than it is easier to implement than what I would consider normal multi-select behaviour. Multi-selection should be enabled by holding down the ctrl or shift key to select non contiguous or contiguous rows like every other application on earth. Using the mouse in this manner also prohibits the ability to drag rows which has also been raised on this forum. Lastly, almost every js based grid I've ever seen, KendoUI included cannot handle multi-select AND virtual paging. Once selected rows go out of scope, they will not be re-selected when back in scope. Be the first to market on this feature and trump your competition. It is a hard feature to implement, but one that is surely worth the bragging rights.
When using setOptions and loadOptions to allow users to save their personal configurations of a grid, it would be nice if I didn't have to manually add all of the templates to the options object before calling setOptions. Without that step, columns using view templates appear with the raw data. To add the templates to the options object, I'm forced to separate them out as functions instead of leaving them inline with the column definition.
when putting grid into new item creation state it should be possible to put new item with some predefined fields. Current it is realy difficult to achieve that: using datasource and insert do not contain isNew on model, also put it on top of grid page is difficult, not possible using model.set. on edit event causing fireing save event when it should be fired only when item is realy saved.
The issue is reproducible when the grid consists only from Multi-header columns, the setDataSource() method has been used and one of the columns is initially hidden.
After setting the new data source, the last header gets hidden. The "display: none;" style has been applied to the "th" HTML element.
Steps to reproduce:
1. Create a grid with multi-header columns only.
2. Hide one column initially.
3. Set a new data source via the setDataSource() method.
4. The last column gets hidden.
Sample Dojo:
https://dojo.telerik.com/AcipENOt
Kendo UI version: 2019.1.220
When endless scrolling and grouping is enabled on the KendoUI grid, collapsing large groups causes the grid to load ALL the hidden detail rows into the DOM.
This takes a very long time for the grid to do, as well it violates the whole point of a paging system. (ie I only want you to load X records at a time). Afterwards the performance of entire website (including the grid) will be very poor since potentially thousands of rows have been loaded into the grid and then immediately hidden. Additionally, these rows do not add any value to the user, since they are all hidden anyways.
When a category is collapsed, the grid should NOT add any new rows for that category to the DOM.
I have included a sample that demonstrates the performance issues.
The Grid's pdf.repeatHeaders option does not display the column headers for each new page when exporting the Grid to PDF
Regression introduced with 2023.1.314
The column headers are displayed only on the first PDF page
The column headers should be present for each PDF page