Last Updated: 13 Mar 2017 09:04 by ADMIN
Formulas like =0.0001/10 or formulas that produce small values results in 0 instead of exponential numbers.

Available in LIB version: 2017.1.313
Last Updated: 11 Dec 2018 15:22 by ADMIN
ArgumentException with clarification similar to  "'\u001f', hexadecimal value 0x1F, is an invalid character." is thrown when trying to export document containing characters which are not supported in XML document - such as some control characters like 0x00, 0x1F, 0x1B, etc. Such characters are described in the XML specification here:

Although the escaped strings are not supported (see ), the library could prevent the exception and export the document successfully by skipping such characters.

Workaround: remove such characters before the export. Check the following StackOverflow answer for some ideas on code for replacing the characters:

Fix available in R3 2018 SP1 release.
Last Updated: 31 May 2016 17:18 by ADMIN
Last Updated: 22 Jun 2020 14:39 by ADMIN
Release R3 2020
Currently, the calculation of the actual ScaleFactor is based only on Worksheet`s UsedCellRange.
Last Updated: 11 Jan 2019 12:35 by ADMIN
When a chart is inserted in a document, generated by SpreadProcessing or WordsProcessing, the chart seems to lack any bars. The reason is that some theme information is missing, which effectively makes shapes take their default color, which is transparent. The same applies for shapes inserted in any Document Processing-generated OOXML documents - docx, xlsx.

Workaround: (applicable for Excel) Manually change the theme for the document in MS Excel:
- Choose Page Layout -> Themes -> Themes dropdown -> Office.
Last Updated: 17 May 2018 08:04 by ADMIN
KeyNotFoundException is thrown on import. The number formats with id 5, 6, 7 and 8 are missing in the built-in number formats.

Available in R2 2018 Official Release version.
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.
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. 
Last Updated: 19 Oct 2018 11:08 by ADMIN
Created by: Polya
Comments: 0
Category: SpreadProcessing
Type: Bug Report
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.
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.


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)
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.
Last Updated: 05 Nov 2019 14:58 by ADMIN
Release LIB 2019.3.1111 (11/11/2019)
The exception is thrown when importing a document that contains a not supported BuiltInNumberFormat.
Last Updated: 26 May 2020 09:05 by ADMIN
Release LIB 2020.2.525 (05/25/2020)
Last Updated: 16 Sep 2020 12:41 by ADMIN
Release R3 2020
Created by: Dimitar
Comments: 2
Category: SpreadProcessing
Type: Bug Report

To reproduce: 

- Add the following formula to a cell: "=A1=FALSE"

Actual: the result is always false

Expected: the result should be true when the cell is empty


Workaround: Use the ISBLANK function.

Last Updated: 21 Aug 2020 10:19 by ADMIN
Release R3 2020
Exception when the sheet name contains a single letter 
Last Updated: 02 Jul 2020 12:01 by ADMIN
Release R3 2020
When a formula contains new lines, it is parsed incorrectly as follows:

- When it is shared formula it breaks the imported expression and replaces it with #NAME? error.
- In normal case it simply preserves the formula string converting it to StringExpression.

Workaround: Remove the new lines in the formulas.

Have in mind that this code will fix the issue only for the second scenario, when the formula is not shared.

CellRange usedCellRange = workbook.ActiveWorksheet.UsedCellRange;

for (int row = usedCellRange.FromIndex.RowIndex; row < usedCellRange.ToIndex.RowIndex; row++)
    for (int column = usedCellRange.FromIndex.ColumnIndex; column < usedCellRange.ToIndex.ColumnIndex; column++)
        CellSelection cell = workbook.ActiveWorksheet.Cells[row, column];
        ICellValue value = cell.GetValue().Value;

        if (value.RawValue.Contains("\n"))
            cell.SetValue(value.RawValue.Replace('\n', ' '));
Last Updated: 20 Jun 2016 13:19 by ADMIN
Last Updated: 22 Feb 2017 11:54 by ADMIN
When there is a defined name referring many cells with long values, the Value of the defined name is string which does not contains the values of all the referred cells and ends with "...".
Last Updated: 13 Oct 2016 06:51 by ADMIN
The way the RadSpreadProcessing decides if a row should be exported works slow. It iterates through all the rows in the UsedCellRange and checks if some property is set and if not, checks if some cell is set. This is slow because each row is checked one by one.
Last Updated: 22 Feb 2017 11:54 by ADMIN
Xlsx documents with global print area defined cannot be imported. Message box "The name that you entered is not valid." is shown and internally SpreadsheetNameException is thrown. 
By default, print areas are defined in the xlsx files for specific spreadsheet:
<definedName name="_xlnm.Print_Area" localSheetId="0">Sheet1!$A$1</definedName>
but this one is without localSheetId property specified.

MS Excel can import such document and even preserve the area, but do not respect it and doesn't have UI to clear it.

By OOXML specification, this attribute is optional:
<xsd:attribute name="localSheetId" type="xsd:unsignedInt" use="optional"/>

Workaround 1 (includes processing the document with MS Excel):
- Open the document in MS Excel
- Choose Formulas -> Defined names -> Named Manager
- Choose Filter -> Names with errors
- Find all Print_Area defined names and delete them
- Save the document

Workaround 2:
- Delete all print areas with OpenXML SDK

Available in LIB version: 2017.1.213
1 2