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

Allow customisation of the bool filter in grids.  I.E. implement the UI property that works for other non-checked columns.  The current filter is too wide, does not allow fontawesome characters, etc.

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

Current grid implementation sorts the whole data again and again for each page virtualization. This causes the scrolling stuck. Please think to change the grid implementation so that the scrolling is not stuck when virtualization and sorting enabled.

we are not able to show the whole data object in grid. The detail template helps in this situation. But while editing detail templates are not handy.

When editmode is detail, user should expand the row to edit. To add new record we can show expanded row. It's more of the popup edit but looks good in the UI perspective

Can we please get support for multi-column headers when using Kendo Grid 'Initialization from Table'. We need to be able to display the grand total at the top and have the row fixed. So the only way i thought to achieve this is to included it in the header.

Multiple String searching in standard filter.

Today the basic Grid filter for strings can be used to search for 1 or 2 items at best.  It would be great to be able to filter for > 2 items from 1 column at a time.  

A multicheck box filter does not work so well when you have 100k+ items, and the multicheckbox ends up with 1000s of items in it.  A string search is more appropriate for the end user.

Our current grid a user can filter for upwards of 500 strings of text in one column by treating the input as a textarea that is styled to auto-grow and is not resizable.

If Column widths are not set, The grid column and column header will be misaligned when autoscroll is enabled unless the following code is used which feels like a hack. This code snippet was given to me by a support team member.

    dataBound: function(e)
    {
      
        if($(".k-grid-content table").height() > $(".k-grid-content").height())
        {
          	$("#grid1 div.k-grid-header").css('padding-right',kendo.support.scrollbar());

            $("#grid1 div.k-grid-content").css('overflow-y', 'visible');  
        }
       	else
        {
            $("#grid1 div.k-grid-header").css('padding-right', '0');

            $("#grid1 div.k-grid-content").css('overflow-y', 'hidden');        
        }
    }

The data-cascade-from-field option requires a DOM id to function. Due to the nature of in-cell editing, the DropDownList appears only when the field is clicked.

A potential fix would be to allow us to configure cascade through the model rather than the UI.

The Grid should optionally select an entire row instead of individual cells within a row.

Use Case:
In my app, the cells are all read-only. Below just about every grid in the app is a details view (showing the selected grid row) and I want them to have up/down keyboard navigation on every grid within the app. This should be a simple configuration setting but there is currently no easy way to get this behavior.