Bug 76389 - Calc: Used AutoFilter not highlighted when set in Calc and saved as XLS
Summary: Calc: Used AutoFilter not highlighted when set in Calc and saved as XLS
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: Other All
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: implementationError
Depends on:
Blocks: XLS-Autofilter
  Show dependency treegraph
 
Reported: 2014-03-20 10:25 UTC by a07cd040897db54e103c
Modified: 2023-04-26 11:40 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
AutoFilter natively set with MS Excel. (18.00 KB, application/vnd.ms-excel)
2014-03-20 10:27 UTC, a07cd040897db54e103c
Details
AutoFilter changed with Calc, saved as XLS. (6.00 KB, application/vnd.ms-excel)
2014-03-20 10:27 UTC, a07cd040897db54e103c
Details
A screenshot of the missing filter highlighting. (17.80 KB, image/png)
2014-03-20 10:28 UTC, a07cd040897db54e103c
Details

Note You need to log in before you can comment on or make changes to this bug.
Description a07cd040897db54e103c 2014-03-20 10:25:46 UTC
When an autofilter is used in a table (natively created with ms excel and saved as xls) then Calc correctly applies AND highlights the *used* filter (colors the normally black arrow into blue).

If you then change the filter using Calc and save the file as XLS, reopening in calc correctly *applies* the formerly defined filter, but does not longer *highlight* which filters are used.

This is very annoying, especially when many columns contain filters.
Comment 1 a07cd040897db54e103c 2014-03-20 10:27:02 UTC
Created attachment 96090 [details]
AutoFilter natively set with MS Excel.
Comment 2 a07cd040897db54e103c 2014-03-20 10:27:44 UTC
Created attachment 96091 [details]
AutoFilter changed with Calc, saved as XLS.
Comment 3 a07cd040897db54e103c 2014-03-20 10:28:29 UTC
Created attachment 96092 [details]
A screenshot of the missing filter highlighting.
Comment 4 a07cd040897db54e103c 2014-03-20 10:30:32 UTC Comment hidden (obsolete)
Comment 5 A (Andy) 2014-03-21 21:51:25 UTC
reproducible with LO 4.2.2.1 (Win 8.1)
Comment 6 Timur 2014-10-20 11:07:43 UTC Comment hidden (obsolete)
Comment 7 ign_christian 2014-10-22 02:57:04 UTC
Anyway it's not correctly applied if we resave file in comment 1 as XLS. 

Hit the dropdown arrow and we can see all numbers (from 1 to 5) checked. What is displayed (4 only) is incorrect.

Tested with LO 4.2.7.2 - Ubuntu 12.04 x86
Comment 8 ign_christian 2014-10-22 03:03:30 UTC Comment hidden (obsolete)
Comment 9 tommy27 2014-12-03 02:45:34 UTC
I can reproduce it under Win8.1x64 using LibO 4.3.3.2 and 4.5.0.0.alpha0+
Build ID: f20043a0805c3a75eb4024ed59f45291aea93ac0
TinderBox: Win-x86@39, Branch:master, Time: 2014-12-03_01:16:50
Locale: it_IT

moving it to mab4.3 list since 4.2.x is EOL
Comment 10 Tom Colley 2016-02-29 20:11:45 UTC
I can confirm issue still exists today for LO on Ubuntu 14.04, LO Version: 4.4.5.2, Build ID: 40m0(Build:2).
Comment 11 mahfiaz 2016-08-05 16:50:59 UTC
Still an issue in 5.2.0.4
Comment 12 QA Administrators 2017-09-01 11:19:49 UTC Comment hidden (obsolete)
Comment 13 a07cd040897db54e103c 2018-06-20 14:49:46 UTC Comment hidden (obsolete)
Comment 14 a07cd040897db54e103c 2018-12-21 09:22:03 UTC
retestet with:

Version: 6.1.3.2
Build-ID: 1:6.1.3-2
CPU-Threads: 2; BS: Linux 4.18; UI-Render: Standard; VCL: x11; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded

and 

Version: 6.0.6.2 (x64)
Build-ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77
CPU-Threads: 16; BS: Windows 6.1; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE); Calc: group

=> problem still exists in both cases
Comment 15 Timur 2018-12-21 16:33:34 UTC
Started from 3.5 when AutoFilter was improved to include multiple values. Repro 6.3+. Even worse with XLSX.
Comment 16 a07cd040897db54e103c 2023-03-21 14:15:06 UTC
retestet with:

Version: 7.0.4.2
Build ID: 00(Build:2)
CPU threads: 16; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Debian package version: 1:7.0.4-4+deb11u4
Calc: threaded

=> problem still exists
Comment 17 ady 2023-03-21 16:41:54 UTC
I can reproduce it in:
Version: 7.0.4.2 (x86)
Build ID: dcf040e67528d9187c66b2379df5ea4407429775
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

...but not in:
Version: 7.4.6.2 (x64) / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
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

I have not tested versions in between.

To be clear, if I open attachment 96090 [details] with LO 7.0.4.2, change the filtered values and save it (with a different name), close everything and then I open the newly saved xls file with either LO 7.0.4.2 or with LO 7.4.6.2, then it will still show the autofilter arrow in the original black color, and new filtered values will be shown as expected.

If, instead, the whole procedure is performed by LO 7.4.6.2, then not only the filtered values are shown as expected but the filter arrow is shown in blue, as expected.

Lastly, repeating the procedure in LO 7.4.6.2 from the original xls but saving in xlsx with modified filtered values also resulted in the same expected results.

Thus, this seems to be WFM as of 7.4. Ideally, the original reported should try to confirm this by using an updated version of LO if possible, after patiently waiting for 9 years and updating this report to see this happening.

To the original reporter:
 I am setting the report to NEEDINFO. Please set to WORKSFORME if you are able to confirm with a newer version, or to NEW if it still doesn't work for you in a newer (maintained) version.
Comment 18 a07cd040897db54e103c 2023-04-26 10:29:14 UTC
retestet with:

Version: 7.4.5.1 / LibreOffice Community
Build ID: 40(Build:1)
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Debian package version: 4:7.4.5-2
Calc: threaded

=> problem is FIXED!

Thank you!