[Update as of 11:42 EST: It appears this may only impact workbooks in the SpreadsheetML (XML) format. This may not be an issue for XSLX native format. We are working to confirm.]
We are running into a major problem that appears to exist in Aspose.Cells for .Net up to version 18.104.22.168. I see nothing in release notes since then that addresses this, either.
The problem is that a new feature in MS Excel is being rolled out to users at different paces, in support of dynamic arrays. Users aren’t notified and have no choice as to whether they accept it or not. It’s the Implicit Intersection Operator. More info here: https://support.microsoft.com/en-us/office/implicit-intersection-operator-ce3be07b-0101-4450-a24e-c1c999be2b34?ui=en-us&rs=en-us&ad=us
One user may have a version of Excel that supports implicit intersection operators. The root of the problem is that when an Excel file is opened by a user on this new version, all formulas of a certain type automatically have @ symbols inserted into them, in order to support dynamic arrays.
For example, if I, as a user of Excel that does not support the implicit intersection operator feature, am working in a workbook and enter a formula of “=IF(ISERROR(INDEX(B89:AW92…etc)”, and then send a copy of the file to someone else who is on a version of Excel that DOES have this feature, then when they open the file, that formula becomes “[=@IF(ISERROR(@INDEX(B89:AW92…etc)](mailto:=@IF(ISERROR(@INDEX(B89:AW92…etc))”.
If that user then uploads the file to our application to be processed by Aspose.Cells, then it causes an error because Aspose.Cells does not handle those @ symbols, and thinks it’s an invalid formula.
I’m surprised there is nothing already in the forums or on google about this. It’s starting to wreak havoc on our implementation of Aspose.Cells.
Is anyone else having this issue? Is Aspose aware? Is there an ETA to address?