Description: After defining a "cell range" data validity in a sheet and then copying that sheet, the data validity is RIGHT in the new sheet. If you then delete the original sheet, the data validity is WRONG in the new sheet. Instead of containing valid entries, the selection list contains only "#REF!". Steps to Reproduce: 1. Load the attached spreadsheet. 2. On Sheet2, observe that D1’s selection list works correctly. 3. Delete Sheet1. 4. On Sheet2, observe that D1’s selection list now works incorrectly. Actual Results: After deleting Sheet1, Sheet2.D1's selection list contains only "#REF!". Expected Results: After deleting Sheet1, Sheet2.D1's selection list should still contain "aaa", "bbb", and "ccc". Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: From "Help / About LibreOffice": Version: 6.3.6.2 (x64) Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded OS: Microsoft Windows 10 Home, Version 10.0.19041 Build 19041
Created attachment 163992 [details] Spreadsheet with data validity already defined This spreadsheet was created as follows: 1. Create a new spreadsheet. 2. In cells A1, B1, and C1, enter “aaa”, “bbb”, and “ccc”, respectively. 3. In cell D1, select “Data / Validity…” On the Criteria tab of the Validity dialog, allow a “Cell range”, and choose “Show selection list”. Specify a source of A1:C1. 4. On the original sheet’s tab, choose “Move or Copy Sheet…”. Copy the original sheet to a new sheet. 5. Save this spreadsheet.
There should not be a problem because copying the sheet the relations betweens cells break up. I can not reproduce your bug on linux. Tested on Version: 6.4.5.2 Build ID: a726b36747cf2001e06b58ad5db1aa3a9a1872d6 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US Calc: threaded
Reproduced. Versión: 6.4.6.1 (x64) Id. de compilación: 985dd72ca280d5c6da2e9f90f7ff9286cafe7ff8 Subprocs. CPU: 4; SO: Windows 10.0 Build 20180; Repres. IU: predet.; VCL: win; Configuración regional: es-ES (es_ES); Idioma de IU: es-ES Calc: threaded But after see the @REF, going to Menu/Data/Validity [Ok] works fine again.
Miguel, what should Richard to do in this case?... It is a bug, or it is something Richard could do?...
Dear Richard Kelly, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The bug is still present with the latest version of LibreOffice. I created a new, test spreadsheet by following the steps listed in comment 1. Then I reproduced the problem by following the steps listed in the original description. I got the same result as before, i.e. Sheet2.D1's selection list contains only "#REF!". From my Help/About LibreOffice dialog: Version: 7.3.5.2 (x64) / LibreOffice Community Build ID: 184fe81b8c8c30d8b5082578aee2fed2ea847c01 CPU threads: 8; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Any suggestions for fixes or workarounds would be greatly appreciated. Thank you!
Reproducible with: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 540a312af2f02108ea90f5d2a9f3bf573db622e5 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded But after see the @REF, going to Menu/Data/Validity [Ok] works fine again.
The "Menu/Data/Validity [Ok]" thing is a decent workaround; thank you. Might it also be a clue to the root cause? After the error is introduced, the behavior seems consistent with the spreadsheet holding two versions of the Data Validity attributes, i.e. the human-readable version we see in the dialog and an encoded version cached internally. Does selecting the dialog's [Ok] button cause the software to re-interpret the human-readable version and store the result internally? If so, would re-interpreting it earlier (e.g. when deleting Sheet1) fix the bug? The above is just speculation. I haven't seen the relevant code. I'm just basing my speculation on the behavior I've observed.
Still repro Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5cd9de202765e243e41416802f3e4486b8a96f16 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL threaded Built: 2023-04-21