Incorrect formula value after calling Worksheet.CalculateFormula

Hi,

After calling Worksheet.CalculateFormula the value of a formula is changed and wrong.
For reproducing the issue please use the attached XLSX file and the following code:

var excelDocument = new Workbook(“PivotFormula.xlsx”);
var worksheet = excelDocument.Worksheets[0];
var value = worksheet.Cells[“J5”].DisplayStringValue;
Console.WriteLine(“Before Worksheet.CalculateFormula: {0}”, value);

worksheet.CalculateFormula(true, false, null);

value = worksheet.Cells[“J5”].DisplayStringValue;
Console.WriteLine(“After Worksheet.CalculateFormula: {0}”, value);


Best regards,
Aurelian Iordache
Software Developer
IBM Romania

Hi,

Thanks for your posting and using Aspose.Cells.

We were able to observe this issue after executing your sample code with your source excel file using the latest version: Aspose.Cells
for .NET v8.4.2.2
. The value of cell J5 should be calculated as True but it is calculated as False.

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-43667 - Incorrect formula value after calling Worksheet.CalculateFormula

Hi,

Thanks for your using Aspose.Cells.

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

Hi,


As discussed with the support, can you please release this build (Aspose.Cells for .NET v8.4.2.5 ) with .net 3.5?

Thank you,
Ruxandra

Hi,


Please wait a few days (2-5 days hopefully) as we are scheduled to release our next official version of the product: Aspose.Cells for .NET v8.5.0, so you may download/ install and get your required .NET framework version once we publish the release.

You will also get automatic notification about the next official version (build/update) once it comes out for the users.

Thank you.

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


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