ImportData into a spreadsheet can remove a formula in adjacent cell

We are in the process of updating Aspose.Cells from v19.1 to the latest version in our .NET application, and testing it on existing data.
We met a case where the use of ImportData call on a spreadsheet removes a formular from a cell which should not be affected by the call.
Note that previous versions of Cells, up to v20.8.0, work correctly.

I attach a program which replicates the issue. It contains a spreadsheet with several formulas in range D2:D5, like this:
image.png (7.0 KB)

We import a data table with 3 rows and 2 columns into cell A4. And check values in column D of the spreadsheet - cell D4 has no value and no formula.

Note that sample program includes two such spreadsheets, one of them does not have such problem, though both look exactly the same. They were edited differently.
I hope the test code is self-explanatory.

We would appreciate a fix for this regression.
BugReplication_1283897189.zip (16.0 KB)

@solvexia
By using sample code and file for testing, we can reproduce the issue. It was found that after calling the ImportData method to import data into Excel, the formula in adjacent cell was removed.

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-55068

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.

1 Like

@solvexia,

This is to inform you that your issue (logged earlier as “CELLSNET-55068”) has been resolved. The fix will be included in the upcoming release (Aspose.Cells v24.2) that we plan to release in the next week. You will be notified when the next version is released.

Great job - thanks a lot.
Looking forward to the new release.

@solvexia
You are welcome. Once Aspose.Cells v24.2 is released, we will notify you promptly.

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