Forum Discussion
dakuhlke
Oct 22, 2019Copper Contributor
Implicit intersection operator: @ breaking my formulas
Contrary to Microsoft claiming: " It's important to note that your formulas will continue to calculate the same way they always have.", this is not the case. The introduction of the @ symbol in versi...
mathetes
Oct 22, 2019Silver Contributor
Are you able to provide a sample of this in context -- i.e., can you share a sample of the actual formula in the spreadsheet/workbook of which it's a part.
And, ideally, provide an English language translation of what this formula is doing, the different results it delivers under different conditions. It's hard enough reading nested IF and MATCH conditions in a formula one has written oneself; next to impossible to read what another developer has done.
And, ideally, provide an English language translation of what this formula is doing, the different results it delivers under different conditions. It's hard enough reading nested IF and MATCH conditions in a formula one has written oneself; next to impossible to read what another developer has done.
ScottP-F
Feb 18, 2021Copper Contributor
In my workbook, it changed several formulas like "=IF(G2 = "Yes", "", D2)"
to
"=IF(G2 = @Yes,"",D2)"
Completely breaking the functionality of my workbook. In each case, the referenced value was *NOT* an array, nor part of an array formula.
Fortunately, the bulletin seems to be inaccurate in at least one regard. On save/re-open, my manual fixes of the formulas were not converted to legacy array formulas.
A method of disabling this automatic conversion should have been provided, along with an explicit warning to the user in the application that this was taking place at the time it happened.