IF any custom validation available for spreadsheet cells, then while exporting the sheet, those validation error messages or formats not getting exported. So here it will be helpful if its exports validations too. So user can see error in both UI and Exported file. In the below example, user can see the error messages in ui but cant see on the exported file. https://docs.telerik.com/kendo-ui/controls/data-management/spreadsheet/how-to/validation-to-column
In MS Excel when you type a number you can easily go to other cells by using the arrow keys and type in another number, thus allowing for fast editing of the spreadsheet. This does not work in the spreadsheet component. this functionality only needs to work when not creating a formula.
Client-side exported Excel workbooks are exported "uncompressed" (as readable text) and their size is much greater than the original document.
Regression since R2 2019 - 2019.2.514
When a cell/row is selected, its first cell is focused and the sheet is scrolled to show it. If a long sheet is scrolled down/right to edit cells, this scroll top/left is very annoying and user unfriendly.
In these scenarios Excel focuses the topmost/leftmost currently visible cell, avoiding sheet scrolling.
NOTE: for rows reproduction select cell AX2, then click on the header of row 2 - sheet is scrolled to the left and cell A2 is focused.
Column C is selected, cell C1 is focused and the sheet is scrolled to top.
The used has to scroll down to the bottom row again to edit data at the bottom of the sheet.
Column C is selected. The currently visible topmost cell of column C is focused, without scrolling the sheet. Excel works that way
The current client-side export functionality does not preserve the number of columns.
Load the following file in the Spreadsheet which contains columns up to "BA".
Export the file
Load the file again in the Spreadsheet and notice that the columns are displayed up to "AX" instead of "BA".
Client-side export does not preserve the number of columns greater than "AX".
Client-side export does not preserve the exact number of columns.
Wanting to format a subset of a single cell with text styling different from the rest of the cell contents. Something like the following:
The Spreadsheet widget is a good start, here are some additional ideas: 1) Ability to assign specific data columns to a spreadsheet column in DataSource data binding and format them. 2) Control tools that can be visible in the toolbar as well as add custom toolbar items/tabs 3) Enabled/Disable or Show/Hide tabs in tool bar. Alternatively, be able to add custom tabs and toolbar items as well. 4) Events! need more events. Cell selected, Range selected, column selected, etc... 5) Disable/Enable certain commands (such as Cut, Copy, Paste, Delete) based on #4 or other criteria. Useful if I do not want specific cell or column data copied or deleted.
It should be possible to define cell types (or types that are valid for the entire column) like: - Booleans (which will result in showing check boxes inside the cells)
Currently the spreadsheet dynamically creates the FilterMenu for a range, that is, it's not created until someone clicks the filter dropdown, and it's destroyed if they switched tabs. There is no event that is fired when these things happen, which makes it hard to attach to, and customize, the FilterMenu without setting up some crazy listening code (setTimeout, etc.). It would be great if either (or both: - You could specify a template for the filter menu. - You could listen for a "FilterMenu Initialized" event and capture the menu there and customize it.
Custom editors are great! But often when you have a custom editor, you want to restrict data entry to only use that editor, and not free-form typing in the cell. You can prevent free-form typing in the cell by disabling the cell, but then the custom editor button is no longer available. Suggestion is to still show custom editor button even if cell is disabled, perhaps with an additional setting; so that you could optionally not show the custom editor if the cell is disabled, since often a disabled cell should prevent any kind of modification.
Allowing custom editors to be inline would be very helpful. In particular, inline editors using other Kendo controls (e.g. masked textbox, numeric textbox) should be possible.
Currently if you access cells range programmatically, you can set background color, text color etc. It would be good to have the way to set classes or to get the DOM of the range. Another option would be to get DOM or set a class to individual cells (e.g. via range.forEachCell).
We have clients with large spreadsheets that print out across multiple pages, which can mean losing track of which column refers to what on new pages after a page break, so they want to be able to assign a row of column headers to be printed on new pages above each column to keep track