When working with kendoGridGroupBinding the collapseGroup API does not work. It would be nice if we had the ability to collapse the grid programmatically rather then having the user close all the groupings manually.
i am using Telerik Angular Editing Grid for list editing of data.one of our main requirements is to copy a cell value and multiselect cells to paste data. this requires Angular grid to provide out of the box multi cell selection mode so that upon action respective cell values get updated
Setting grid.columns[i].hidden may work to some extend, but isn't emitting columnVisibilityChange and further activities on a column set visible are not working but resulting in error, e.g. calling reorderColumn() results in:
TypeError: Cannot set property 'orderIndex' of undefined
at GridComponent.push../node_modules/@progress/kendo-angular-grid/dist/fesm5/index.js.GridComponent.updateColumnIndices (https://localhost:4201/vendor.js:196833:43)
The grid internal method updateColumnIndices() throws an error, because it doesn't get the newly visible column from expandColumnsWithSpan() and expandedColumns.indexOf(source) is -1.
Thus it's required to add methods like showColumn/hideColumn or setColumnVisibilty.
I believe it would be a great addition and simplification, if there were getOptions/setOptions methods at GridComponent to imperatively access/restore grid state (visibility, column order, sort order, filter, ...). These are also available at Kendo UI for jQuery.
I know, all the settings may be set using *ngFor and *ngIf directives, but that approach requires a lot of attribute remapping (from component instance to template) which doesn't feel right, especially when using column templates and and a lot of grid features.
When using virtual scrolling and the data changes, then it might be desireable to programmatically scroll to top or to scroll to a row containing the data of interest.
Our application uses grouped grids but doesn’t use the built-in collapse feature. We instead hide the collapse arrow to disable the option. This leaves an empty space to the left of the parent grid label (where the collapse arrow would normally sit) and an empty column on the left side of all child grids. We’re looking for a more “official” and supported way of achieving the effect that removing ‘[group]=“groups”’ currently achieves. We’d like to minimize the amount of nonstandard code we’re introducing to our Kendo implementation as well as minimize unintended consequences of altering the grid code.
If the value "-1" is passed in as one of the values in pageSizes input for the PagerPageSizesComponent, that option should be shown as "All" and should show all rows available for the grid.
Basically whats described in this issue right here: https://github.com/telerik/kendo-angular/issues/2093
It would be nice if column group visibility could be toggleable via the column chooser.
If not, a more elegant workaround would be to indicate in the column chooser that certain columns are part of column groups. The way it is now is too clunky and unclear.
For example, I have the following column groups:
But the above columns show up in the column chooser like so:
It would be nice if the column group name was at least prepended to child columns in the column chooser to at least indicate that it's part of a group. For example, it would show as follows instead:
[x] Latest read - Time
[x] Latest read - Value
[x] Latest write - Time
[x] Latest write - Value
Thanks so much.
Hey Kendo Team,
you already have a solution in jQuery for my problem (https://docs.telerik.com/kendo-ui/knowledge-base/grid-group-remove-footer-header-one-record).
Unfortunately this solution did not work in Angular.
Desirable solution would be a flag in GroupHeaderTemplate which removes header if group size is one.
Another solution could be; allow a class field in GroupHeaderTemplate, so that we can set display to none if group size is one.
Please add a template about custom hierarchy cell template.
We have to add few icons in it and also before it and we would like to use angular native way.
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.
It would be nice to have support for horizontal virtual scrolling for the Grid in cases of large number of columns. Just like the current feature for vertical scrolling, in which you can update the visible rows through a pageChange() event handler.
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.
We started using Kendo Grid extensively. We came across below requirement and confirmed with your support team that the feature is currently not available. We think this would really allow users customise their display.
We would be using a common wrapper class across the org.
We will be displaying list of records from the DB, at times, there are columns which contains a JSON, we need to use a custom template to display the JSON. I understand I can go with an if condition in the template html of grid, but, that would lead me to end up having N number of conditions since we do not have a limited such use cases, each such instance would need to be rendered with different template.
The same is the case with row editing as well, for instance, for columns which accepts a description, we want to show a custom popover which would allow the user to specify the data in the way the customer wants (rich text with lot of customisation)
At a high level if we nail down into steps of the behaviour
1) Columns definition will come as a JSON which would also contain a template reference for any of the columns.
To elaborate more, If firstName and lastName are the columns at the DB level but for grid view I want to show them as a single column.
2) The JSON we are constructing will have a type attribute which would indicate me on whether to use a user defined template or regular one.
3) Corresponding data will be a JSON with possible keys required for the template.