Cell's value display abnormal after remove excel formulas using Aspose.Cells

Aspose.Cells Product Family
1

I hava a excel file that contains some Formulas,After remove formulas using Aspose.Cells,The cell display abnormal.

Version info:

Aspose.Cells for Net 23.1.1

The demo:

void Main()
{
	Aspose.Cells.Workbook workBook = new Aspose.Cells.Workbook(@"C:\demo.xlsx");

	//If remove this line,It display normal
	workBook.CalculateFormula();

	workBook.Worksheets[0].Cells.RemoveFormulas();
	
	workBook.Save(@"C:\output.xlsx");
}

The demo file:

demo.7z (13.7 KB)

The screenshot:

20230201213252.png (25.5 KB)

2

We have found the issue and opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSNET-52691

You can obtain Paid Support services if you need support on a priority basis, along with the direct access to our Paid Support management team.

3

Thanks for the reply, I think this is a very serious bug, I hope it can be fixed as soon as possible. Thanks again.

4

@sullivan,

Thanks for sharing your concerns.

We will try to figure out your issue soon. Once we have an update on it, we will let you know.

5

Thanks again!

6

@sullivan
You are welcome!

7

@sullivan,

We have fixed the issue about formatting number values. The new fix will be included into our next official release 23.2 which may be released this week or next week.

Please note, the calculated results of your formulas depend on regional settings. So, to get the expected result as you shown in the screenshot, you need the correct regional settings for your application(such as the culture info of the current thread). Or, you may specify it at workbook level, by Region or CultureInfo. And you code will look like:

Aspose.Cells.Workbook workBook = new Aspose.Cells.Workbook(@"C:\demo.xlsx");
workBook.Settings.Region = CountryCode.China;
workBook.CalculateFormula();
...
8

The issues you have found earlier (filed as CELLSNET-52691) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi