SpreadProcessing: The colors of the chart are not imported correctly.

The columns of the sheet are split when exporting to PDF.

Wrong measured column width when exporting to PDF after binaries version 2019.2.624.

The exception is thrown when importing a document that contains a not supported BuiltInNumberFormat.

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.

Filter Selection dialog appears on the screen. 

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

It takes ~42 seconds to remove each 100th row from a document with 50000 rows and 100 columns.

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:

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. 

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.

If the lookup_value parameter and lookup_vector parameters refer cells containing text values, the function returns a Not available error ("#N/A").

ArgumentException is thrown when importing documents containing empty values

The value formula =Round(1.015, 2) returns 1.01 which is incorrect. Excel returns 1.02.

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.

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: https://www.w3.org/TR/xml/#charsets.

Although the escaped strings are not supported (see  https://feedback.telerik.com/Project/184/Feedback/Details/190228 ), 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: http://stackoverflow.com/a/14323524/259206

Fix available in R3 2018 SP1 release.

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.

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.

Closed as duplicate. Please, follow the item at https://feedback.telerik.com/Project/184/Feedback/Details/190249 .

When the workbook contains multiple styles (e.g. 50000), the import is extremely slow. MS Excel loads this document instantaneously.

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.