Completed
Last Updated: 16 Oct 2019 12:50 by ADMIN
Release R3 2019 SP1
While importing the arguments of the data validation rule, the formula is treated as text and its separators are replaced with the list separator defined in the current culture. This leads to an invalid formula treated as a list of strings.
Approved
Last Updated: 02 Oct 2019 12:37 by ADMIN
Created by: shashidhar
Comments: 0
Category: SpreadProcessing
Type: Bug Report
1

Filter Selection dialog appears on the screen. 

Workaround: Open the file with Excel and save it as a new document.

Approved
Last Updated: 06 Aug 2019 12:51 by ADMIN
Created by: Brittany
Comments: 0
Category: SpreadProcessing
Type: Bug Report
2
It takes ~42 seconds to remove each 100th row from a document with 50000 rows and 100 columns.
Approved
Last Updated: 10 Apr 2019 14:35 by ADMIN
Exporting empty workbook without any worksheet is not allowed according to the specification and such documents cannot be opened in Excel. Ensure the customers cannot create such documents using the API of SpreadProcessing.
Approved
Last Updated: 18 Mar 2019 14:01 by ADMIN
Created by: Stephen
Comments: 0
Category: SpreadProcessing
Type: Bug Report
0
If the lookup_value parameter and lookup_vector parameters refer cells containing text values, the function returns a Not available error ("#N/A").
Completed
Last Updated: 13 Mar 2019 12:14 by ADMIN
ArgumentException is thrown when importing documents containing empty values
Completed
Last Updated: 06 Mar 2019 07:33 by ADMIN
The value formula =Round(1.015, 2) returns 1.01 which is incorrect. Excel returns 1.02.
Completed
Last Updated: 11 Jun 2019 12:46 by ADMIN
Release R2 2019 SP1
The data validation rule should have values for formula1 and formula2 elements, which define the start and end values for a range to validate between. When such values are missing, a NullReferenceException is thrown on import and the document cannot be imported.

Details:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Model.Elements.Worksheets.DataValidationElement.CopyPropertiesToSingleArgumentContext(SingleArgumentDataValidationRuleContext context)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Model.Elements.Worksheets.DataValidationElement.CopyPropertiesToDataValidationRuleContext(DataValidationRuleContextBase context)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Model.Elements.Worksheets.DataValidationElement.ListRuleFactory(IXlsxWorksheetImportContext context)
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.Xlsx.Model.Elements.Worksheets.DataValidationElement.OnAfterRead(IXlsxWorksheetImportContext context)
...
   at Telerik.Windows.Documents.Spreadsheet.FormatProviders.WorkbookFormatProviderBase.Import(Stream input)
Approved
Last Updated: 17 Oct 2018 12:47 by ADMIN
When the worksheet contains fraction numbers with fractional parts > 0.5 and < 0.5 and both these numbers have fraction format applied, the number with fractional part < 0.5 will have incorrect whole part.
Declined
Last Updated: 12 Oct 2018 22:22 by ADMIN
Closed as duplicate. Please, follow the item at https://feedback.telerik.com/Project/184/Feedback/Details/190249 .
Approved
Last Updated: 03 Oct 2018 15:51 by ADMIN
When the workbook contains multiple styles (e.g. 50000), the import is extremely slow. MS Excel loads this document instantaneously.
Completed
Last Updated: 19 Oct 2018 11:08 by ADMIN
ADMIN
Created by: Polya
Comments: 0
Category: SpreadProcessing
Type: Bug Report
1
Incorrect calculation of Round function returns wrong results in some cases. For example, test Microsoft Excel and Spreadsheet results of: ROUND(1.365, 2) to see the discrepancy.

Available in R3 2018 SP1 release.
Approved
Last Updated: 21 Sep 2018 13:02 by ADMIN
When inserting cells a check is performed for data loss. This check should take into account the value property, but should not take into account properties like cell value format and data validation. 

Workaround: clear the values at the end of the worksheet before inserting cells.
worksheet.Cells[1048575, 0, 1048575, 16383].ClearDataValidationRule();
Approved
Last Updated: 05 Sep 2018 14:44 by ADMIN
When the scale factor of a document is smaller, the borders don't seem to scale correctly when exported to PDF. They appear much thicker than they would when exported from Excel.
Approved
Last Updated: 30 Aug 2018 08:04 by ADMIN
When a worksheet has name that has spaces and a hyperlink to this worksheet is being inserted in Excel, quotes are used to surround the name (ex: 'Sheet 12'!A1) for a valid hyperlink. If quotes are not added, the hyperlink is invalid.
In RadSpreadsheet, it is the opposite: (Sheet 12!A1 is correct, while 'Sheet 12'!A1 is incorrect).
Thus, opening such an exported document from RadSpreadsheet in Excel loads it with incorrect hyperlinks; and importing such an Excel document in RadSpreadsheet loads it with incorrect hyperlinks.

A way to workaround this issue is to modify the hyperlinks on import/export from/to RadSpreadsheet. You can find attached a project demonstrating this approach.
Approved
Last Updated: 21 Aug 2018 10:56 by ADMIN
Having cell with custom format string set to "MMM" does not apply correctly. Instead of showing the date in the defined format (for instance "Aug"), what actually is displayed is "MMM".
Approved
Last Updated: 31 Jul 2018 07:27 by ADMIN
When the automatic scaling options FitToColumns and FitToRows are used, the vertical and horizontal breaks, respectively, should be ignored.

Workaround:

Remove the page breaks if the worksheet uses automatic scaling and restore them if necessary:

        public void ExcelToPdf(string path)
        {
            var provider = new XlsxFormatProvider();
            using (Stream input = File.OpenRead(path))
            {
                var workbook = provider.Import(input);

                this.CachePageBreaks(workbook);

                var pdfProvider = new PdfFormatProvider();
                pdfProvider.ExportSettings = new PdfExportSettings(ExportWhat.EntireWorkbook, false);
                using (Stream output = File.Open(@"C:\Users\velcheva\Desktop\26293903-c650-4d28-adee-58a542651f72_exceltopdf\exported.pdf", FileMode.Create))
                {
                    pdfProvider.Export(workbook, output);
                }

                this.RestorePageBreaks(workbook);
            }
        }

        private Dictionary<Worksheet,List<PageBreak>> verticalPageBreaksCache;

        private void CachePageBreaks(Workbook workbook)
        {
            this.verticalPageBreaksCache = new Dictionary<Worksheet, List<PageBreak>>();

            foreach (Worksheet worksheet in workbook.Worksheets)
            {
                WorksheetPageSetup pageSetup = worksheet.WorksheetPageSetup;

                if (pageSetup.FitToPages)
                {
                    this.verticalPageBreaksCache[worksheet] = new List<PageBreak>(pageSetup.PageBreaks.VerticalPageBreaks);
                    
                    if(pageSetup.FitToPagesWide != 0)
                    {
                        List<PageBreak> breaksToRemove = new List<PageBreak>();
                        breaksToRemove.AddRange(pageSetup.PageBreaks.VerticalPageBreaks);

                        breaksToRemove.ForEach((br) => pageSetup.PageBreaks.TryRemoveVerticalPageBreak(0, br.Index));
                    }

                    // Record the horizontal page breaks if necessary.
                }
            }
        }

        private void RestorePageBreaks(Workbook workbook)
        {
            foreach (Worksheet worksheet in workbook.Worksheets)
            {
                WorksheetPageSetup pageSetup = worksheet.WorksheetPageSetup;

                if (pageSetup.FitToPages)
                {
                    List<PageBreak> cachedbreaks = this.verticalPageBreaksCache[worksheet];

                    if (pageSetup.FitToPagesWide != 0)
                    {
                        foreach (var pageBreak in cachedbreaks)
                        {
                            pageSetup.PageBreaks.TryInsertVerticalPageBreak(0, pageBreak.Index);
                        }
                    }

                    // Restore the horizontal page breaks if necessary.
                }
            }
        }
Completed
Last Updated: 23 May 2019 13:14 by ADMIN
When the worksheet contains many formulas which use large ranges (e.g. covering 50000 cells) as arguments and these formulas have to be calculated, this causes OutOfMemoryException. 
Approved
Last Updated: 25 Jul 2018 12:53 by ADMIN
The named ranges need to be translated when used in a certain cell just like the data validation rules.

WORKAROUND: When you use RowSelection.Insert() method, for instance, after the row insertion you may iterate all defined names in the document. Parse their RefersTo property and if it is affected by the insertion, delete and recreate the DefinedName in the corresponding NameCollection by updating the RefersTo text value. Sample code for parsing the RefersTo property may be seen in the description of this feedback item: 

https://feedback.telerik.com/Project/184/Feedback/Details/190061-spreadprocessing-add-api-to-get-the-list-of-ranges-to-which-a-defined-name-refer
Completed
Last Updated: 01 Oct 2018 14:00 by ADMIN
When the values that were copied have formatting both on the cell and on the column, the pasted values get the formatting of the column, instead of that of the cell. The same applies to rows.
1 2 3