Distinguish between cse legacy array formula and normal array formula

Aspose.Cells Product Family
1

How can i check if a array formula is a cse legacy array formula or a normal array formula?

I made an excel file with both

            var workbook =
                new Workbook(@"\ArrayFormulas.xlsx");
            
            Worksheet sheet1 = workbook.Worksheets[0];

            Cell cellA12 = sheet1.Cells["A12"]; // {=SUM(A2:A10*B2:B10)} cse legacy formula
            bool isArrayFormulaA12 = cellA12.IsArrayFormula;
            // true
            Cell cellB12 = sheet1.Cells["B12"];
            bool isArrayFormulaB12 = cellB12.IsArrayFormula; // =SUM(A2:A10*B2:B10)
            // true

ArrayFormulas.zip (7.2 KB)

Both cells are arrayformulas, but I can’t see which formula is the cse formula.

After I extract the excel xml data.
ArrayFormulas.png (45.7 KB)
And open the xml in a editor I can se that the normal array formula has as attribute on the cell xml cm=“1”. Is there a function to maybe read that attribute?

Is there a way to know if a formula is legacy formula or normal formula?

2

@perfectxl,

I evaluated your requirements a bit but could not find relevant API to distinguish or differentiate between CSE legacy array formula and normal array formula. I have logged a ticket with an id “CELLSNET-52022” for your issue/requirements. We will investigate in details if we can add some attribute to distinguish a cse legacy array formula and normal array formula. We will look into it soon.

Once we have an update on it, we will let you know.

3

@perfectxl,

This is to inform you that your issue has been resolved now. The fix will be included in our upcoming release (Aspose.Cells v22.11) which is scheduled in the first/second week of November 2022. You will also be notified when the next version is released. Please note, in the next version, we will provide new API: Cell.IsDynamicArrayFormula to indicate whether the cell’s formula is dynamic array formula(true) or legacy array formula(false).

4

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