Description: VSLOOKUP: "0" is not false Steps to Reproduce: https://help.libreoffice.org/Calc/Spreadsheet_Functions#Syntax_2 "Enter the Boolean value FALSE or zero if the first column is not sorted in ascending order." "FALSE()" works but "0" does not. "0" still expects the first to be sorted. And by the way that is "FALSE()" not "FALSE". Please correct either the program or the documentation, which ever is incorrect Actual Results: see above Expected Results: see above Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 152758 [details] vlookup test case >"FALSE()" works but "0" does not. "0" still expects the first to be sorted. i can not confirm with: Version: 6.2.5.2 (x64) Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: Linux only problem?
(In reply to Oliver Brinzing from comment #1) > Linux only problem? It was reported to me from a Windows user
(In reply to Todd from comment #2) > It was reported to me from a Windows user so can you please check with attached document or attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
The document is full of private and proprietary information. Give me a little bit to recreate the document with Larry, Curry, and Moe as the principles. In the mean time, this is the offending formula: =VLOOKUP($A$7,$Pilots.$A$2:$Pilots.$B$21,MATCH($Pilots.B1,$Pilots.$A1:$Pilots.$B$1,0),FALSE())
[Automated Action] NeedInfo-To-Unconfirmed
Oh you know what, I 1) created a special spreadsheet with the formulas in it and could not reproduce the issue, and 2) tried to reproduce the issue with the original corrected spreadsheet and also could not. I do believe what transpired what that they are using this spreadsheet directly from drop box and something got corrupted. (Bad idea to use drop box like that.) And the act of modifying the formula re-saved it correctly back to the spreadsheet and corrected the issue. So lets go ahead and close as INVALID. If it pops up again, I will get back. Thank you all for your assistance and patience with this issue. :-)