We now have operators that support filtering for null/empty values in grid columns. These are available using the standard Filter Menu, which provides input fields and the operator dropdown list. Our users really love the Multi Checkbox filtering, which allows them to choose any number of possible values at the same time. The missing feature is that the Multi Checkbox filtering prevents us from finding the "empty" rows. Much the same way that "Select All" is automatically added to the list of checkboxes, please add some sort of "null/empty" item to the list. It would be great if this was configurable. In some of our columns, it's not possible to have empty values, so it doesn't make sense to include the "empty" checkbox for those columns. Be sure to handle scenarios when the data source is automatic based on the data in the grid and when a separate, custom data source is provided for the column.
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") ));
It would be nice to have an option to place the filter row in the table footer instead of the header. It is possible to move it in the DOM using JavaScript, but it breaks the functionality.
Dear Telerik, I assume, there should be one button in kendoUI grid to scroll to bottom of grid and one button to scroll top of grid in just one click. Similarly one button to scroll extreme right and one button to scroll left of grid. These buttons can be near, vertical scroll button and horizontal scroll buttons. Regards Surinder
Please implement multi-row drag-and-drop in the Grid widget.
in a grid configured to groupable = false using a datasource that is grouped will allow selecting a grouping row, it does not show in the ui, but the select() method will return the grouping row. demo: http://dojo.telerik.com/aDevo code: <!-- shows problem with select() in grid where dataSource is grouped and groupable is disabled --> <!-- in the demo it is possible to select the grouping row which is not shown but select() returns the grouping row as selected, the problem is even worse if using multiselect with ctrl and clicking on the grouping row --> <!DOCTYPE html> <html> <head> <meta charset="utf-8"/> <title>Kendo UI Snippet</title> <link rel="stylesheet" href="http://kendo.cdn.telerik.com/2016.1.412/styles/kendo.common.min.css"/> <link rel="stylesheet" href="http://kendo.cdn.telerik.com/2016.1.412/styles/kendo.rtl.min.css"/> <link rel="stylesheet" href="http://kendo.cdn.telerik.com/2016.1.412/styles/kendo.silver.min.css"/> <link rel="stylesheet" href="http://kendo.cdn.telerik.com/2016.1.412/styles/kendo.mobile.all.min.css"/> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> <script src="http://kendo.cdn.telerik.com/2016.1.412/js/kendo.all.min.js"></script> </head> <body> <div id="grid"></div> <script> var dataSource = new kendo.data.DataSource({ data: [ { productName: "Tea", category: "Beverages" }, { productName: "Coffee", category: "Beverages" }, { productName: "Ham", category: "Food" }, { productName: "Bread", category: "Food" } ], group: { field: "productName" } }); $("#grid").kendoGrid({ selectable: "multiple, row", allowCopy: true, groupable: false, columns: [ { field: "productName" }, { field: "category" } ], change: function (e) { console.log("number of selected items: " + e.sender.select().length ); }, dataSource: dataSource, }); </script> </body> </html>
If another value gets created, we want to be able to update the columns.values array without destroying the grid and recreating it.
Hi, I posted an issue in forum thread. http://www.telerik.com/forums/grouping-with-column-template-not-working I'm stuck because grouping is not working on template column containing null values. Is it possible to get a working solution? It seems to be a simple null check not done in kendo framework... Thank you for your help
Currently the grid only includes row virtualization. Column virtualization would be really beneficial for projects that display many columns
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); }
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.
We are running into a situation where our users need to copy values from a row in a Grid. The Grid also uses multiple row selection, and the allowCopy is getting in the way by copying too much data onto the clipboard. Would it be possible to set a field list in the options for allowCopy so that we can specify which columns are actually copied? Example: allowCopy: { delimiter: '\t'. fields: [ 'column1', 'column2' ] } We are also running into another situation where we need to use templated fields, and allowCopy seems to be copying the cell text resulting in very ugly clipboard data. It would be nice if we could specify the datasource value to be copied instead of the cell text Example: allowCopy: { delimiter: '\t'. fields: [ { field: 'column1', source: true }, { field: 'column2' } ] } In both examples, the field name corresponds to the field name specified for the Grid Column.
We are not using an editable grid for this scenario. The Kendo Grid needs to have its existing filter and sort cleared which should not result in two unnecessary reads to the server and then do a read on the datasource to get the newly added row. We then return the data from the server in descending order by Id so the new row is at the top of the grid and selected. If the sort for a default view and add are the same, no issues, but when they are not, the work around is complex. What are the options and how can we make this simple task simpler to code and maintain?
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.
For kendo grids, it would be really useful to be able to have a right-click on the grid to select the row. I know there is a fudge to do this but it would be useful to have different actions for a left and right click, e.g. a context menu on right click instead of left.
Need Control + F function to search the text in the Grid When we have more records and enabled virtual scrolling ,the data which is not present the view is currently not searchable using CTR+F. We need to get this enabled where finds the data and scroll down to the specific row.
Have a simple Boolean option that tells the filter to either use or ignore the time portion of a filter on type 'date'. Filtering 'exactly' on date and time is almost useless, whereas filtering on a day provides useful information.
Kendo UI Grid should have a option to set confirmTemplate options to show custom confirm window. Now browser ugly built-in prompt is awful.
To have a paging option based on the alphabetical order for certain column instead of number paging