The return value for function ERROR.TYPE when the search is out of range is #N/D but must to be 7 (as Excel). Before, the function ERROR.TYPE was different in Calc and Excel, the returned values was 32767, 532, 502 or 504 in Calc while in Excel was 7,2,7,4 in different errors. Steps: Create new Calc sheet: Write in cells: Column A Row 1: =VLOOKUP("Don't exist",B129:B131,1,0) Row 2: =5/0 Row 3: =VLOOKUP("Out of range",B121:B123,2,0) Row 4: =#REF! Column B Row 1: =ERROR.TYPE(A1) Row 2: =ERROR.TYPE(A2) Row 3: =ERROR.TYPE(A3) Row 4: =ERROR.TYPE(A4) results in B1-B4 in Calc: 7,2,#N/D,4 with ERROR.TYPE, and results in Excel: 7,2,7,4. Ok, in the help says: "If the ERROR.TYPE function is used as condition of the IF function and the ERROR.TYPE returns #N/A, the IF function returns #N/A as well. Use ISERROR to avoid it as shown in the example above." But the behaviour is different in Excel-Calc. The old function is named ERRORTYPE (without dot, in spanish translation is TIPO.DE.ERROR.OOO) and the result is: 32767, 532, 502, 504 for errors A1 until A4. En la vera internacia lingvo: Esperanto, kiu diskriminacias malpli pro denaska lingvo: La valorezulto por la funkcio ERARO.TIPO (ERROR.TYPE en la angla) kiam la serĉo estas ekstere de ĉelintervalo estas #N/D sed ĝi devas esti 7 (kiel Excel). Antaŭe, la funkcio ERARO.TIPO estis malsama en Calc kaj Excel, la valorrezultoj estis 32767, 532, 502 aŭ 504 en Calc kaj en Excel estis 7,2,7,4 en malsamaj eraroj. Paŝoj: Kreu novan Calc-folion: Skribu en ĉeloj: (apartigilo , povas esti ; laŭ lando) Kolumno A Vico 1: =VSERĈO("Ne ekzistas",B129:B131,1,0) Vico 2: =5/0 Vico 3: =VSERĈO("Ekstere de ĉelintervalo",B121:B123,2,0) Vico 4: =#REF! Kolumno B Vico 1: =ERARO.TIPO(A1) Vico 2: =ERARO.TIPO(A2) Vico 3: =ERARO.TIPO(A3) Vico 4: =ERARO.TIPO(A4) rezultoj en B1-B4 en Calc: 7,2,#N/D,4 kun ERARO.TIPO, kaj rezultoj en Excel: 7,2,7,4. Bone, en la helpo diras: "If the ERROR.TYPE function is used as condition of the IF function and the ERROR.TYPE returns #N/A, the IF function returns #N/A as well. Use ISERROR to avoid it as shown in the example above." Sed la konduto estas malsama en Excel-Calc. La malnova funkcio nun estas nomata ERARTIPO (sen punkto, en la angla ERRORTYPE kaj en la hispana traduko estas TIPO.DE.ERROR.OOO) kaj la valorrezultoj estas: 32767, 532, 502, 504 por eraroj A1 ĝis A4. Y en español: El valor de retorno para la función TIPO.DE.ERROR (ERROR.TYPE en inglés) cuando la búsqueda está fuera de rango es #N/D pero debe ser 7 (como en Excel). Antes, la función TIPO.DE.ERROR era diferente en Calc y Excel, los valores devueltos eran 32767, 532, 502 o 504 en Calc, mientras que en Excel era 7,2,7,4 en diferentes errores. Pasos: Crear nueva hoja de cálculo: Escribir en celdas: (ojo, el separador puede ser , o ; según el país) Columna A Fila 1: =BUSCARV("No existe";B129:B131;1;0) Fila 2: =5/0 Fila 3: =BUSCARV("Fuera de rango";B121:B123;2;0) Fila 4: =#¡REF! Columna B Fila 1: =TIPO.DE.ERROR(A1) Fila 2: =TIPO.DE.ERROR(A2) Fila 3: =TIPO.DE.ERROR(A3) Fila 4: =TIPO.DE.ERROR(A4) los resultados en B1-B4 en Calc: 7,2,#N/D,4, y los resultados en Excel: 7,2,7,4. resultados en Calc en versiones anteriores y en Calc ahora con TIPO.DE.ERROR.OOO Bien, en la ayuda dice: "Si la función TIPO.DE.ERROR se usa como condición de la función IF y TIPO.DE.ERROR devuelve # N / A, la función IF también devuelve # N / A. Use ISERROR para evitarlo como se muestra en el ejemplo de arriba ". Pero el comportamiento es diferente en Excel-Calc. La función antigua se denomina TIPO.DE.ERROR.OOO (en inglés ERRORTYPE sin el punto separador) y el resultado es: 32767, 532, 502, 504 para los errores A1 hasta A4.
already reproducible with Version: 5.4.7.2 Build-ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU-Threads: 4; BS: Windows 6.2; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: single
Created attachment 146724 [details] error.type example
https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr1.cxx?r=4ddd6f32#7186 https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr4.cxx?r=32d846dc#1912 https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr1.cxx?r=4ddd6f32#9663 https://opengrok.libreoffice.org/xref/core/sc/source/core/tool/interpr1.cxx?r=4ddd6f32#9674
Also reproduced in Version: 5.2.0.0.alpha0+ Build ID: 54862a932fc9ccc1788e91629818ec6666ec1c09 CPU Threads: 4; OS Version: Linux 4.15; UI Render: default; Locale: ca-ES (ca_ES.UTF-8) @Eike, I thought you might be interested in this issue...
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.
Dear gmolleda, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Created attachment 155964 [details] view error The bug continues in LO 3.3.2