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.
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.
I have experience creating column groups at the top of a kendo grid, but I would now like to do something similar with row groups. I have attached a screenshot of an example of what I would like to accomplish. Is this possible with Kendo Grid?
When in Kendo-Grid for Angular there more columns then that fits in the page, we get a horizontal scroll.
If i apply reordering of columns and try to move one to any direction.
1. If the columns need to be moved on same visible section, it does moves perfectly.
2. but if i want to move something beyond the visible section, i can't as the scrolling does not work automatically, either i need to use Keyboard to move scroll bar which in case users needs to be trained or is not user friendly or i need to it in parts.
Please help us to include feature to auto scroll when we move columns
When grouping one column on a large table, all rows (groups) are expanded by default which consumes CPU/memory. Render time grows. Please add bool property defaultCollapsed. In this case grid would not expand all rows(groups) by default. Current work around is to call collapseGroup, but performance would be a lot better if rows could be collapsed by default.
Kendo Angular PDF is currently has good functionality to export/download as PDF. My Idea is that , if Kendo can extend its PDF export functionality with print also. Problem - Currently using kendo PDF download, the GRID or any HTML component looks good to the users. But the same Grid if the user want to print , then the developers has to use some third party scripts to generate the print object and do the print. still its not appears as good as it appears in PDF. so the end users are complaining why the PDF export and the print is different in look and feel. Here are the steps to overcome. 1. should have a print PDF functionality which opens the PDF into new window. 2. the user has the option to download or print the pdf using PDF in-built options. 3. Kendo to provide fix to open in new window for all browsers ( IE, chrome, firefox etc) 4. Kendo print should not send the request to underline printer or any other hardware device.
hello i`m always using kendo grid in my project but i can`t import excel to kendo grid please make it possible to import excel file and select specific sheet to kendo grid
Add the RowTemplate feature of JQuery Grid to Angular Grid. https://demos.telerik.com/kendo-ui/grid/rowtemplate In particular we are looking to be able to define 2 rows of data per row. The second has cells that span multiple columns so we are unable to achieve what we want with a Cell Template ( https://www.telerik.com/kendo-angular-ui/components/grid/columns/templates/ ).
It is difficult to move a column beyond the columns that are currently visible without using the horizontal scroll. So as column are listed in the drop down it would be good to be able to reorder here. Could also implement the auto scrolling of the horizantal scroll when moving column beyond the visible scroll. Both would be good.
Please add support to change order of filter/clear buttons in Grid Filter Menu Component (so instead of "Clear-Filter" button order we can use "Filter-Clear" button order).
Exporting grid and chart in single pdf. If we have grid and chart in seperate tab. With hidden content what if we have a pagination in grid and want complete grid and chart. https://stackblitz.com/edit/angular-8tdtwv-p6r75m?file=app/app.component.ts
In a Kendo grid, Angular/MVC/JS/Whatever; When using multi check filter. ---- Only show those values that are still useful to filter on!!! --- When filtering is done(one to many columns) - ONLY the remaining options should be seen when setting the NEXT filter (not all possible values in the database) of course distinct and sorted (the grid could have an option of doing it this way or the old way) example: let's say we have 5 numbers of categories, each category have 20 different details. when filtering is set on one category, then when filtering on details - only the 20 remaining details should be seen, not 100(5*20) and vice verse, if filtering one detail - only one category should be seen when filtering on category.
when expanding a group, inside the expand event (function) we do have access to the groupIndex. but groupIndex is not available inside the groupHeader(Footer)Template itself. we need that groupIndex, so we can get the parent items (groups) to the group that is expanded.