In Grid inline editing right now when we click on  addnew row ,new row is adding as the first row of grid. can we get feature like when we can add new row at specific position in the grid

Currently the pager is always at the bottom of the grid. I would love to see an option to place the pager at the top and/or bottom. Without adding custom code every time I need this.

Any plans on creating a Distinct Filter for the grid? 

One like Wijmo has?  https://ibb.co/fo7gwQ

Currently, the auto resize of the the columns does not take the width of the grid into account.  I don't think this is how most users would expect this to work.  The autofit of the columns should be able to resize the columns so that they work as best they can within the grid's bounds.

Now, when I autofit my columns, the first thing I have to do is resize the columns manually so I can see the whole row on the screen.  Since I end up resizing the columns manually anyway, autofit ends up not really helping me much.

Some toolkits I have used have a resize mode for a table which determines whether or not all columns are to always be visible or not.  If all the columns are to always be visible, resizing one column needs to resize the others so that everything still fits.  This "mode" could determine which algorithm autofit should use

Hello,

As discussed with Martin in support ticket 1429284, some of the column values in my grid might be the same, but with different letter cases. For example, column "First Name" could have the values "Elias", "elias", and "ELIAS".

When grouping, Kendo grid grouping treats those values as 3 separate groups because its case sensitive. Our users expect those values to be grouped as 1 to avoid confusion. 

The workaround provided might affect other dependent features and make the code a bit messy.

I would appreciate it if you could add in a future version, a built in option to ignore case when grouping without changing the original displayed values.

Regards,
Elias

Now I can configure possible filter operators and default operator on column basis. Doing so I have much copy-pasted code for each grid column.

I want to have a grid level option to configure this on "type" basis with a reusable js object (e.g. public constant shared across components):

<kendo-grid [filterOptions]="GridFilterOptions" ...

Where GridFilterOptions:

public const GridFilterOptions: ... = [
{ type: "string", default: "contains", operators: ["contains", "doesnotcontain"]},
{ type: "number", default: "eq", operators: ["eq", "neq"]}
];

Add icons for grid filter operators to easily understand current operator (DevExpress example):

https://gyazo.com/3806906633b2c1ca66f6cacc2b32ba88

Add "between" grid filter row operator similar to DevExpress for angular one.

Example here:

https://js.devexpress.com/Demos/WidgetsGallery/Demo/DataGrid/Filtering/Angular/Light/

We recently had an ask to limit the number of columns that could be selected, and were not able to find an out of the box solution (nor was support).

Something like this would be great, which is the same implementation as the kendoGridFilterMenuTemplate which allows you to override just the content of the column chooser, and not have to manually create your own menu entry by overriding the whole kendoGridColumnMenuTemplate

<ng-template kendoGridColumnChooserMenuTemplate let-service="service">
    <our-custom-chooser-component></our-custom-chooser-component>
</ng-template>

or, alternatively, if we were able to specify a grid parameter for a max number of columns as a grid level [maxColumns], that would work as well.

Hello,

I would like to request a way to have the selected/unselected column menu sorted separately from the table's columns.

Here is our table which demonstrates the current behavior.

When first rendered on the page:

After re-arranging the columns:

However, it'd be nice to have the column menu sorted separately from the table's columns. Thank you.

When using KendoUI for Angular 2+, the filter value is still enabled and accepts input when "Is null" or "Is empty" is selected.

Since those selections do not require a parameter, I'd prefer the filter value to be default disabled.