//with .Net 6, x64, Aspose.Cells 24.10.0
Workbook wb = new Workbook(@"Test.xlsm");
wb.Settings.FormulaSettings.EnableCalculationChain = true;
Worksheet sh = wb.Worksheets.Last();
for (int col = 0; col < 5; col++)
{
sh.Cells[5, col].Value = null;
wb.CalculateFormula();
}
@Zhigang_Wang,
Thanks for the template XLSM file.
After initial testing, I am able to reproduce the issue as you mentioned by using your template XLSM file. I found System.NullReferenceException is thrown when setting cell value with FormulaSettings.EnableCalculationChain = true.
We require thorough evaluation of the issue. We have 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-57077
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.
Thank you for replying.
How can I track this issue by its ID, and how many issues are ahead of it in the queue?
@Zhigang_Wang,
Please note, issue tracking system is internal, so you cannot track it. You are always welcome and ask us to get latest updates on the issues. Please spare us little time to evaluate your issue thoroughly and then we will be able to provide updates on it. If the issue is not complex, it will be figure out quickly. If it is complex, it might take a few weeks or more time to resolve it. In any case, once we have an update on your issue, we will update you.
1 Like
@Zhigang_Wang,
We are pleased to inform you that your issue (Ticket ID: “CELLSNET-57077”) has been resolved. The fix/enhancement will be included in the upcoming release (Aspose.Cells v24.11) scheduled for the next week of November 2024. You will be notified when the new version is published.
The issues you have found earlier (filed as CELLSNET-57077) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi
Thank you! I tested it and everything is OK now!
@Zhigang_Wang,
Thanks for your feedback.
Good to know that the new version fixes your issue. You’re welcome to reach out to us again if you have any other questions or feedback.