Removing worksheets generates XLSX that fails when opened in Excel

The following API calls produce the failing XLSX when applied to the attached file:


workbook.Worksheets.RemoveAt(11);
workbook.Worksheets.RemoveAt(3);
workbook.Worksheets.RemoveAt(2);
workbook.Worksheets.RemoveAt(1);
workbook.Worksheets.RemoveAt(0);

It seems to be a common type of bugs, please take a look. The issue observe with Aspose.Cells v8.6.

Hi Dmitry,


Thank you for sharing the sample for our testing.

We have evaluated the presented scenario while using the latest version of Aspose.Cells for .NET 8.6.0.5 against the following piece of code, and we are able to notice the problem, that is; the resultant spreadsheet cannot be loaded with Excel without repair. We have logged this incident in our bug tracking system as CELLSNET-43991. Our product team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for your inconvenience.

C#

var workbook = new Workbook(“D:/ABSSalesTradingTrace.xlsx”);
workbook.Worksheets.RemoveAt(11);
workbook.Worksheets.RemoveAt(3);
workbook.Worksheets.RemoveAt(2);
workbook.Worksheets.RemoveAt(1);
workbook.Worksheets.RemoveAt(0);
workbook.Worksheets.ActiveSheetIndex = workbook.Worksheets[“Weekly Chart Data”].Index;
workbook.Save(“D:/output.xlsx”, SaveFormat.Xlsx);

Hi,

Thanks for using Aspose.Cells.

This is to inform you that we have fixed your issue CELLSNET-43991 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.6.0.7 and let us know your feedback.

Thanks, it fixes the issue.

Hi,


Thanks for your feedback.

Good to know that your issue is figured out by the latest version/fix. Feel free to contact us any time if you need further help or have some other issue or queries, we will be happy to assist you soon.

Thank you.

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


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

The issues you have found earlier (filed as ) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by MuzammilKhan