Currently, you cannot disable all columns in the column menu - it requires that at least one column is enabled.
However, if the grid contains any non-hidden columns which have IncludeInMenu=false, then it should be possible to disable all the remaining columns using the column menu.
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
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!
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.
It would be nice to have the option for a single filter input that searches all columns on the Grid. I was able to implement my own custom solution but having to apply that to every grid in my app is cumbersome. I understand the importance for the flexibility side of having each column with its own filter box, but for simpler apps this is overkill and a single filter box is enough. The column component already has the [filterable] flag so this can possibly be used to exclude any columns if necessary. I was thinking of something similar to what is an out of the box feature for the Datatables JS plugin https://datatables.net/ Default search box that searches everything. Very simple to use and understand for basic users or when your application only calls for something that simplistic.
I was working with Sencha ExtJS and they have to option to make components "stateful" (http://docs.sencha.com/extjs/6.2.0/classic/Ext.state.Provider.html). This will safe user modified settings in browser (defaults to cookie but you can provide your own implementation). Example (for grid): * we specify width=100 for first colum * we allow users to resize columns * If a users resizes a column the new width will be stored in state * ... if the user later opens the page again, values from state will overwrite "defaults" from code. If we use this for column width, visibility and order we've a perfect customizable grid view.
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.
Please check out a bug in the material design theme for grid pageing combobox in mobile device. You can check this bug at http://demos.telerik.com/kendo-ui/grid/remote-data-binding you have to adjust "mobile:true" option and then run by mobile simulator instead of web. When you change the page with combobox. Grid's height will be reduced by combobox height. This bug occured only in material design theme. (I didn't check all theme. I checked material, default, bootstrap, nova, fiori, office365)
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.
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.
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.
Excel-like filter always show all available options. When one filter was already applied - could we limit number of options to see only options that are left after previous filtration? We should be able to filter only by already filtered rows. As alternative - could we have some event on Excel-like filter to populate options for it every time it expands?
Currently, kendo-styled checkboxes are not rendered for the default column editors for Boolean columns. Instead, default browser checkboxes are rendered. In addition, kendo-styled checkboxes are not supported (and indeed do not function correctly) in custom column editors. This issue creates a styling consistency "blemish" on pages where we've otherwise been totally consistent with a Kendo theme. Please alter the grid behavior so that it both renders Kendo-styled checkboxes for the default Boolean column editor, and allows them for custom column editors.
The End-User experience for multiple column sort is awful. Please provide a UI that lets them see & change the columns they are sorting by. Current problems are: 1. If the user is sorting by 3 columns. All they see is 3 columns with an up/down arrow. There is no visual indication of the actual sort order (Col1, Col2, Col3) or (Col2, Col3, Col1). 2. Lack of Control. This gets more confusing if you have 3 columns in a sort, then click Col2, until it is not sorted. Then click it again to make it sort ascending. I assume it drops out of the sort, & is then added at the end. Making sort = (Col1, Col3, Col2). This confusion forces you to clear everything & start the sort again. 3. Inability to clear quickly. But there is no UI that offers the user a quick way to Unselect all sorted cols, so they can start the sort selection process again. Clearly we can add something to the toolbar, but ideally they wouldn't need to clear & restart their sort selection. . 4. Unpredictable outcome. It is not obvious to the User how to control the order of the multi-column sort. How does the sort get determined? :- A. First column selected becomes the Primary order, the next col is the Secondary order. eg: select Col1, then col2, then col3, to get (Col1, Col2, Col3) order. OR B. Last column selected is the Primary. eg: select Col3 then col2, then col1 to get (Col3, Col2, Col1) order. 5. Server/Database cost. Sorting & network round trips are expensive. Toggling from Asc / Desc / Clear. Is expensive & slow compared to setting all the columns once & clicking OK. 6. I'd add a mockup image, but this feedback screen doesn't permit uploads. To get an idea of a potential UI, Try sorting on multiple columns in Excel. It shows like a tree, with the primary key at the top, the secondary a line lower, followed by the less significant keys below it. OR at min. Change the Arrow into an Arrow with a tiny number (1,2,3 etc) 7. The current approach you use to add the Sort icon is really annoying to the user, especially when they have many narrow columns of numbers. Be aware that when you add the sort icon, converting a Label into something with 3 "..." chars is unnecessary. We found it cleaner to just truncate the chars that didn't fit, the user gets to see 2 more letters of the label. Which may be enough for them to know which column it is. And it is obvious that the column was too small to display more text. The large padding to the left of the "ColumnMenu" icon is part of the problem, it could be much smaller. 0.5 to 0.25 char width is sufficient. We did a lot of usability testing around this for a different control. The outcome was nearly unanimous in favor of the change above. PS: I too could see benefit in having the sort indicator display to the left. But the changes above may reduce the need a bit..
The refresh button availability should be indepent from the grid being pageable. The user may want an updatable grid without having page navigator.