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.

For example, if a user wants to set a 5x5 array of values in the worksheet he has to iterate through all the values one by one and set it to the worksheet. With that API the user should be able to set the entire array with just one method call giving it the array.

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.

The item is closed as duplicated of https://feedback.telerik.com/Project/184/Feedback/Details/190065-spreadprocessing-implement-right-to-left-direction.

Add support for preserving and exporting the macros in a macro-enabled workbook.

Macros are pieces of code written in Visual Basic for Applications (VBA) which are used to automate repetitive tasks in excel. The macros are part of the excel file. When a file contains a macro its extension becomes xlsm.

SpreadProcessing should be able to import and export xlsm files and edit the macros in them.

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 "...".

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

The exception is thrown when importing a document that contains an empty stylesheet tag in its styles.xml part.

Define name which we can import looks like this:

<definedName name="Test">Sheet1!$A$1</definedName>

The case which can not be handled by RadSpreadProcessing looks like this:

<definedName name="Test"><![CDATA[Sheet1!$A$1]]></definedName>

The CDATA element is used to escape the inner text in order not to be parsed as XML. That means this is а valid case, and RadSpreadProcessing should handle it.

Add support for the AVERAGEIF function:  https://support.office.com/en-us/article/AVERAGEIF-function-faec8e2e-0dec-4308-af69-f5576d8ac642

Returns the average (arithmetic mean) of all the cells in a range that meet a given criteria:

AVERAGEIF(range, criteria, [average_range])


Workaround: This could be implemented as a custom function: http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/custom-functions.html

If shape extent is declared, the two cell anchor points for the drawing element are ignored. For example if the TwoCellAnchorElement's from and two points declare that the image should be anchored starting from cell A1to F10 and further in the drawing declaration there is defined extents element with image size values, anchor element's points are ignored. 

Add API for registering custom image decoders, e.g. for .emf and .wmf images.

Add support for the SUBTOTAL function: https://support.office.com/en-us/article/SUBTOTAL-function-7b027003-f060-4ade-9040-e478765b9939

It computes the subtotal for some ranges, given the code for the subtotal function:

SUBTOTAL(function_num,ref1,[ref2],...)

where function_num is code referring to some of the functions: AVERAGE, COUNT, COUNTA, MAX, MIN, PRODUCT, STDEV, STDEVP, SUM, VAR, VARP.

Note that we should implement the support for all of the above functions. As of now, COUNTA, VAR, VARP are not supported.

Workaround: This could be implemented as a custom function: http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/custom-functions.html , but multiple functions (4 as of now) has to be additionally implemented.

When a workbook (xlsx) contains a worksheet where some of the columns have width, bigger than the value written in the SpreadsheetDefaultValues (2000) an exception during the import is thrown.

This will enable printing with the following printing options: 

- Fit Sheet on One Page

- Fit All Columns on One Page

- Fit All Rows on One Page

- Custom automatic scaling


A possible implementation of a similar behavior is to use the PageSize property of WorksheetPageSetup and subtract the corresponding margin values (from the Margins property) from the width to calculate how many columns are fitting in some particular page size with 100% scale factor. 

Available in R2 2018 Official Release version.

Add support for manual calculation option, which allows not to recalculate all the formulas on value change, but on manual request. 

MS Excel supports this feature in Formulas -> Calculation -> Calculation Options, with the following options: Automatic, Automatic Except for Data Tables, Manual.

The cell contains the following data in OOXML:

<f>SUM(1,2,3)</f> - The formula
<v>6</v> - the calculated value

The formula value is imported, but the calculated value is skipped. The feature will be useful if Manual calculation option is supported: https://feedback.telerik.com/Project/184/Feedback/Details/191275-spreadsheet-add-support-for-different-calculation-options-automatic-or-manual

When the column width is not an integer number, but a decimal fraction one, the width which is exported is not calculated correctly. 

For example, if there is a cell with some text and its column's width is autofit, it's exported with different actual width.

In addition, if the exported xlsx file is imported back in the Spreadsheet, the column width is a bit different from the one which was exported (only for the first export-import roundtrip).

When there is some long number value in merged cell and this cell is autofit, then in Excel the cell is visualized with "#####" because the column width is not enough.

Workaround: As a workaround in some scenarios it is possible to call Merge method after AutoFitWidth method in order get the correct column width.