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.

Steps to reproduce: 

1. Enter in a cell =Today()
2. Show Format Cells dialog and set Custom format "d"

Expected: The value is the day of the month.
Actual: The date is formatted as short date but has to be day of the month.

For all characters which cannot be represented in XML as defined by the XML 1.0 specification, the characters are escaped using the Unicode numerical character representation escape character format _xHHHH_, where H
represents a hexadecimal character in the character's value. This is dedined in the OpenXML specification in 22.9.2.19 ST_Xstring (Escaped String).

Currently this causes the following issues:

- Documents conaining such characters are imported incorrectly, e.g. <si><t>_x001B_</t></si> is imported as the plain text _x001B_

- ArgumentException with clarification similar to "' ', hexadecimal value 0x1B, is an invalid character." is thrown when trying to export such documents. Example code to reproduce:

            Workbook workbook = new Workbook();
            Worksheet worksheet = workbook.Worksheets.Add();

            CellSelection selection = worksheet.Cells[1, 1]; //B2 cell
            selection.SetValue(string.Format("Error Value: {0} ", Encoding.ASCII.GetString(new byte[] { 27 })));

            string fileName = @"D:\temp\SampleFile.xlsx";
            IWorkbookFormatProvider formatProvider = new XlsxFormatProvider();
            using (FileStream output = new FileStream(fileName, FileMode.Create))
            {
                formatProvider.Export(workbook, output);
            }

When importing and exporting xlsx document with email address hyperlink the exported document shows invalid document message when opened in Excel: "We found a problem with some content in 'file.xlsx'. Do you want us to try to recover as much as we can? If you trust the source of thes workbook, click Yes.". The document can be only partially recovered and information is lost.

Generating document which consists of merged cells in a row and some values then inserting a row on the top and then exporting the document or setting it to the RadSpreadsheet causes wrong merged cells.

If the generation is done on a workbook which is already set to the RadSpreadsheet everything is OK.

Workaround: The document can be exported and then imported again before the row is inserted.

Add support for pivot tables.