I have eight spreadsheets on a file, and I use VLOOKUP to get some informations from one spreadsheet to another. When VLOOKPUP returns a simple string, a number, a date without formatting, it works as normal. But I have some cells with a specific date format. The other seven spreadsheets use VLOOKUP to get those dates from my first spreadsheet and it works normally, even the date format is transferred to the cells with the VLOOKUP formula, and when it's not, all I have to do is change the formatting of the cell to match the ones with the information I need. The problem happens when the first spreadsheet uses VLOOKUP to get dates from the other seven spreadsheets (from cells with the same date format used on the first spreadsheet), VLOOKUP doesn't report any errors, but the cell which receives the value retrieved by VLOOKUP is filled with what seems to be random numbers like "44624". And changing the cell formatting makes no difference, it'll always show the same numbers, whether using "General", "Number", or the standard "Date" format. The only difference between the two cases, is the number of formulae used. When the other seven spreadsheets use VLOOKUP to retrieve dates from the first spreadsheet they use a simple IFERROR((VLOOKUP)"") combination to replace errors with blanks. But when the first spreadsheet uses VLOOKUP to retrieve dates from the other spreadsheets it uses VLOOKUP inside a quite big combination of concatenation, IFERROR, and VLOOKUP. In those cases there is a VLLOKUP formula for each of the other seven spreadsheets, but only one of them has the information I need, therefore, only one VLOOKUP will work, the others will fail, and IFERROR prevents them for messing the whole formula. This combination already works with no problems to retrive only one string from the other seven spreadsheets to the first one, in thoses cases the "General" formatting is used. But will always fail with formatted dates retrieved from the seven spreadsheets to the first.
Can you attach a sample file, as simple as possible.
Dear henrick.silva, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear henrick.silva, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp