SpreadProcessing: XlsFormatProvider. Exception when importing a specific document - bad function index (188)

Add support for the  CELL formula.

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

Wrong color scheme colors leads to wrong cell coloring on export.

Exception when the comments are imported before the fallback notes.

The colors of the charts are determined by the theme in the default scenario. However, customers can apply any color to the series and the legend respectively. In such cases, RadSpreadProcessing doesn't import the custom colors and uses the ones defined by the theme.

Text is cut off in Net Standard with a specific document.

Currently, the following text filters are not supported in the model:

• begins with
• does not begin with
• ends with
• does not end with
• contains
• does not contain

Currently, adding hyperlinks to images is not supported.

 A long formula is wrongly parsed when importing a particular file.

There are scenarios when the default value of the columns is changed and may be different from 65. However, RadSpreadprocessing always exports the non-custom column values as 65.

WORKAROUND: After importing the XLSX file you may make all columns to have custom values in order to preserve the column widths after the export. The following code snippet shows how this may be achieved for some Worksheet instance:

CellRange usedRange = worksheet.UsedCellRange;

for (int i = 0; i < usedRange.ColumnCount; i++)
{
    ColumnSelection column = worksheet.Columns[i];
    double width = column.GetWidth().Value.Value;
    column.SetWidth(new ColumnWidth(width, true));
}

Add support for the EDATE function.

Use the attached custom function as a workaround.

An InvalidOperationException is thrown when importing XLS document containing Extra Table Data record.

Exporting a workbook that has a data validation rule applied on a cell with hyperlink inside results in an invalid spreadsheet document. Trying to open the result in MS Excel, an error appears and letting Excel repair the content results in a missing worksheet.

Optimize font fallback mechanism.

Currently, in NET Standard, if no fonts are provided on PDF export, while resolving the fonts the application falls back to different fonts multiple times for each cell which causes a decrease in performance.

FormatException is thrown when getting the formatted cell value as string using "H" format.

When importing a xlsm document, an error occurs: "The axes are incorrectly paired." 

Clearing an entire row is too slow.

Sometimes the customers need to obtain the result of a formula without adding it as a value to a specific cell.

Currently, these are the supported image formats:

If we try to import an Excel document containing an image with another format, the following error occurs:

System.Collections.Generic.KeyNotFoundException: 'The given key was not present in the dictionary.'