https://bugs.documentfoundation.org/show_bug.cgi?id=121488
--- Comment #13 from [email protected] --- I think error.type should be compatible (same results) with Excel, while for Calc errors we already have error.type.ooo, which, as you say, is much more detailed. Therefore, to maintain compatibility with Excel when importing an XLSX file, the ERROR.TYPE function should return the same values as EXCEL. (In reply to Eike Rathke from comment #5) > Calc has more detailed errors than Excel. In this case the Err:502 > (IllegalArgument) is because the field index to VLOOKUP() is 2 but there is > only one field. Calc returns #N/A only if the lookup-value is not found in > an otherwise correct context. Excel seems to return #N/A in any error case > of VLOOKUP(). > > Actually ERROR.TYPE() returning #N/A can happen with any of the more > detailed Calc error values because there is no defined mapping (and can't > be), which exists only for the seven error values Excel knows. Mapping > Err:502 to #N/A (=7) is not a solution because in other (or most) context it > may be #VALUE! (=3) instead, or something else depending on what Excel > returns for some function's error (which in most cases #VALUE! isn't helpful > at all). > > This isn't really solvable unless we'd transport additional information with > each error what it might be in Excel in the given context just in case there > would be an ERROR.TYPE() evaluating it. Which I think would be overdone and > I'd rather close this as wontfix. The solution is to have ERROR.TYPE identical to Excel's and ERROR.TYPE.OOO more detailed for us. -- You are receiving this mail because: You are the assignee for the bug.
