Completed
Last Updated: 07 Feb 2020 08:06 by ADMIN
Release 2017.R2
Created by: Andrew
Comments: 0
Category: Grid
Type: Feature Request
5
Currently yo keep the selected row after refresh one needs to store the data first and then loop through all the rows to find it and select it again.
This is because the uid changes after refresh.
This does not work very well with large number of rows.
It would be great to have a setting that allowed the selected rows or cells to be kept after the refresh.
Completed
Last Updated: 06 Feb 2020 15:30 by ADMIN
Release 2018.R3
Created by: Joey
Comments: 13
Category: Grid
Type: Feature Request
83
It should be possible to change the width of a grid after it created.
http://www.telerik.com/forums/change-column-widths-after-grid-created
Completed
Last Updated: 24 Jan 2020 11:22 by ADMIN
Created by: Imported User
Comments: 1
Category: Grid
Type: Feature Request
3
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.
Completed
Last Updated: 24 Jan 2020 07:18 by ADMIN
Created by: David
Comments: 1
Category: Grid
Type: Feature Request
0
Would it be possible to add an option for a top scroll on the grid?
Completed
Last Updated: 23 Jan 2020 15:22 by ADMIN
Created by: Sundar
Comments: 5
Category: Grid
Type: Feature Request
10
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
Completed
Last Updated: 23 Jan 2020 14:48 by ADMIN
Created by: dccxz
Comments: 3
Category: Grid
Type: Feature Request
11
Grid should allow to place images in the header of each column instead of text on per column basis.
Completed
Last Updated: 23 Jan 2020 12:31 by ADMIN
Release 2019.R1
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.  
Completed
Last Updated: 23 Jan 2020 12:11 by ADMIN
Created by: Heiko Falk
Comments: 1
Category: Grid
Type: Feature Request
3
Currently having a column format of "{0:#}" does not infect the filters format. E.g. 5 becomes to 5.00 on blur event in filter dialog. So we have to modify filters behaviour manually which is a pain. Currently we are using this function:


function configureFilterFormatting($grid) {
    var kendoGrid = $grid.getKendoGrid();
 
    kendoGrid.bind('filterMenuInit', function (event) {
        var column;
 
        $j.each(event.sender.columns, function (index, item) {
            if (item.field == event.field) {
                column = item;
                return;
            }
        })
 
        if (!column) {
            throw new Error('Invalid column');
        }
 
        if (column.format) {
            // Transform '{0:#}' in '#'
            var format = column.format.replace(/^{0:/, '').replace(/}$/, '');
 
            event.container.find('[data-role=numerictextbox]').each(function () {
                var $numericTextbox = $j(this);
                $numericTextbox.getKendoNumericTextBox().setOptions({ format: format })
            });
        }
    });
}
Completed
Last Updated: 23 Jan 2020 12:02 by ADMIN
Created by: Morten
Comments: 1
Category: Grid
Type: Feature Request
7
The current implementation of Persist State http://demos.telerik.com/kendo-ui/grid/persist-state isn't meant to save the user state of the grid.

Let me explain.
Currently setOptions() override the options in the grid. That has a rather unfortunate side effect. The Column[{...}] options coming from the server is no longer used (ever) as all column options are now coming from the client. Effectively overriding all column options.

Example:
{
   ...,
   columns: [
      { field: "Name", filterable: false }
   ]
}

This is saved using the current persist state.
Later the backend now supports filtering of the "Name" field, and we change filterable to true. The user will not see this change. Because it's overridden with the column options stored on the client.

It would be nice if this wasn't the case.
Either make a new method get-/setUserOptions() or change the current get-/setOptions() (I cannot figure out the usecase for the current implementation as it to me always would be used for what I've described here - and do a poor job of it)

However we also need to recognize that different options have different life cycles.
For example would I want to save current page, sorting and filters in sessionStorage.
While column order, size and pageSize (don't override, just set. As the range can change) would be saved in localStorage.
So that need to be easy to do.

The last thing we need is an event where it would make sense to call setUserOptions(). For the purpose of loading saved state without having to click a "Load state" button. The event needs to be before the datasource is quried. 
The current dataBinding event doesn't work as it would result in an infinite loop of datasource queries.
Completed
Last Updated: 22 Jan 2020 07:32 by ADMIN
Created by: Imported User
Comments: 2
Category: Grid
Type: Feature Request
23
When you configure a grid date-column with a custom format, the value configured in 'format' is parsed using JSON.parse. This requires the use of double quotes for both keys and values.

var a = "{0:dd/MMMM/yyyy}";    // example from docs
JSON.parse(a);    // SyntaxError: JSON.parse: expected property name or '}'

var b = '{"0":"dd-MM-yyyy"}';
JSON.parse(b);    // jey! 

However, if you use the latter, the generated template goes fubar with the message:

"Invalid template:' ... <td>${kendo.format("{"0":"dd-MM-yyyy"\}",theDataField)}</td> ... "

This makes sense when you look at the quote mismatch..
Completed
Last Updated: 21 Jan 2020 09:35 by ADMIN
Created by: Sarvesh
Comments: 5
Category: Grid
Type: Feature Request
18
Current filter control for a date column only shows a date picker, if the data that's bound to the column also contains the time part then the filters don't work properly. Adding a date time picker would solve the problem.
Completed
Last Updated: 21 Jan 2020 09:25 by ADMIN
Release Sprint8.R3.2017
Created by: William
Comments: 1
Category: Grid
Type: Feature Request
17
We want events for expand/collapse groups in Grid, similar to the existing events for details.
This events will helps us for personalize some funcionalitys.

Thanks.
Completed
Last Updated: 20 Jan 2020 10:39 by ADMIN
Release 2017.R3
Created by: Josetuttu
Comments: 1
Category: Grid
Type: Feature Request
5
Consider a grid with grouping and pagination. When we collapse a group, the items from next page should take up the space left be the hidden rows, i.e., grouping should work across pages and not just the current page. Otherwise, grouping is a useless feature in a grid with pagination. This should work for client as well as server pagination and also for virtual scroll.
Completed
Last Updated: 17 Jan 2020 11:54 by ADMIN
Created by: Imported User
Comments: 1
Category: Grid
Type: Feature Request
1
Currently, the Kendo grid has an option to apply only one type of filtering for a specific column (be it standard filtering or multi-checkbox filtering). 

There is a custom approach which actually builds a custom check box list that is attached to the standard filter. But, there are lot of options that are missing like Select All, Search box etc.

There should be a way where user can apply different types of filter criteria on the same column.
Completed
Last Updated: 17 Jan 2020 11:48 by ADMIN
Release 2018.R1
Created by: Taylor
Comments: 1
Category: Grid
Type: Feature Request
11
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.
Completed
Last Updated: 08 Jan 2020 07:20 by ADMIN
Created by: Babu
Comments: 1
Category: Grid
Type: Feature Request
1
I hope other developers realize the importance of this feature and vote for it.

It would be nice (in fact, important to have) an event that we can hook into, after the Edit event fires but before the editor template (more relevant when the editor is a custom popup template).

Let me explain.  On my custom editor template, I have a few dropdownlists that are not defined as foreign keys from the grid datasource.  The dropdowns are defined on the template, usually with a Read action on it.  This read action fires when the template is rendered.  In the Edit event, I need to set some of the elements as different or hidden or shown based on the selected value from more than one dropdown.  This is needed so that some other elements are shown/hidden when the popup is rendered.  The problem is, The edit event is too early to know the selected items in these dropdowns since the data for these ddls are not loaded yet.  Since I need values from multiple dropdowns, hooking into individual databound events of the ddls won't work either.

So, if we had an event something like "BeforeRender" on the grid that fires after all the datasources are loaded and databound for all relevant elements on the editor template, but before the template is rendered onscreen that would be great.  Then, we can hook into this event and when we do, all the datasources for all the dropdowns, comboboxes etc. are loaded and databound already. We can use the items from these elements to show/hide other elements.
Completed
Last Updated: 27 Dec 2019 13:32 by ADMIN
Created by: Chingis
Comments: 1
Category: Grid
Type: Feature Request
0

Request

I'd like to ask for a demo which utilizes the most up to date approach to creating a Kendo UI Grid using NPM, TypeScript, and in a SharePoint 2019 with a Gulp serve environment. 

Thank you for your consideration!

Completed
Last Updated: 27 Dec 2019 13:27 by ADMIN

Hi Team,

 

We are have gone through the documentation for make specific column editable. We found that we need to make it in schema. As we are using some complex objects along with ODATA expand.

We are unable to maintain or Add all the fields under schema.If we make a editable property of column to Boolean and based on value framework will me either read-only or editable.

 

Consider a scenario like Grid with 10 columns based on quantity, price,discount change need to calculate the tax.

Here tax calculation will be dynamic and some columns we can add on the fly.

In some cases like ODATA expand  if i want to make expanded column to editable then it a tough process to edit

like above situations it will be useful if we make column editable to Boolean for achieve column level editing

 

Thanks

Completed
Last Updated: 18 Dec 2019 16:04 by ADMIN
Release 2019.R3.SP1
Currently, if you use alwaysVisbile=false, the pager disappears on each grid rendering and it's very annoying for the end user. Another strange thing about this pager is the way the logic works behind. If the rows are equal to the page number of rows, currently you'll see the pager, but in fact you don't need it. 
Completed
Last Updated: 13 Dec 2019 14:53 by ADMIN

In the popup edit grid, when the editable: false option is displayed, the portion of the value is at the top rather than horizontal. Can you change it horizontal?
1 2 3