SpreadsheetML to XLSX date format has restricted functionality

Attached is a unit test project I created to demonstrate the restriction in functionality between Aspose.Cells 8.3.1 and 8.7.1/8.8.0. The unit test creates an XLSX file from SpreadsheetML on 8.3.1 and 8.8.0 and compares the outputs, they are different between old and new versions.


We outputted dates in ISO 8601 format in version 8.3.1 and now they are not being treated as dates in the newer versions, just being treated as string, and ignoring the format we apply to it.

Any insight into this change is appreciated.

Hi,

Thanks for your posting and using Aspose.Cells.

We tried to open your xml files in Microsoft Excel 2013 and they did not open because they are corrupt. But they are opened fine in Aspose.Cells and we have compared the older and latest version outputs and found the issue.

We have logged this issue in our database for investigation. We will look into it and fix this issue. Once the issue is resolved or we have some other update for you, we will let you know asap.

This issue has been logged as

  • CELLSNET-44427 - ISO 8601 format dates are being treated as strings instead of dates

We have tested this issue with the following sample code using the latest and older versions and attached the output excel files for a reference.

C#
Workbook wb = new Workbook(“ShortDateFormat.xml”, new LoadOptions(LoadFormat.SpreadsheetML));
wb.Save(“ShortDateFormat-” + CellsHelper.GetVersion() + “.xlsx”);

wb = new Workbook(“LongDateFormat.xml”, new LoadOptions(LoadFormat.SpreadsheetML));
wb.Save(“LongDateFormat-” + CellsHelper.GetVersion() + “.xlsx”);

Hi,

Thanks for using Aspose.Cells.

This is to inform you that we have fixed your issue CELLSNET-44427 now. We will soon provide the fix after performing QA and including other enhancements and fixes.

Hi,

Thanks for your using Aspose.Cells.

Please download and try the latest fix: Aspose.Cells for .NET v8.8.0.4 and let us know your feedback.

The issues you have found earlier (filed as CELLSNET-44427) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.