Bug 113585 - Auto Filter Columns are Treated Separately in the Attached ODS File
Summary: Auto Filter Columns are Treated Separately in the Attached ODS File
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: preBibisect, regression
Depends on:
Blocks: AutoFilter Calc-DataRange
  Show dependency treegraph
 
Reported: 2017-11-02 03:13 UTC by Kevin Suo
Modified: 2021-05-10 08:36 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
test ods file (39.66 KB, application/vnd.oasis.opendocument.spreadsheet)
2017-11-02 03:13 UTC, Kevin Suo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Suo 2017-11-02 03:13:36 UTC
Created attachment 137436 [details]
test ods file

The attached .ods file has two columns of data. In the most recent libreoffice version, these two columns are treated separately when doing auto-filtering.

Steps to Reproduce:
1. Click on the drop-down list to filter-out "201607" in column B.
2. Click on the drop-down list to observe the items as shown in the filter-list in column A.

Current Behaviour:
In step 2, all the items are shown in the filtered list.

Expected Behaviour:
Only 07-2016 is shown in step 2.



Further Information:
Apparently Calc is treating these two columns as separate data:
* If you select cell B1, click the autofilter toolbar icon to remove the autofilter status, only autofilter for column A is removed. It should remove both.
* If you select A1:B3692, then click the autofilter toolbar icon to remove the autofilter, then filter on both columns are removed, but if you click the icon to set autofilter again, then filter is set separately again.

The ods file was generated using LibreOffice, I am not sure which version was used to create this file.
Comment 1 Kevin Suo 2017-11-02 03:15:03 UTC
Version:5.4.2.2
Build ID:22b09f6418e8c2d508a9eaf86b2399209b0990f4
CPU Thread:4; OS: Linux 4.13; UI Rendering:Default; VCL: gtk2; 
Locale: zh-CN (zh_CN.UTF-8); Calc: single

Fedora 26 x64.
Comment 2 Buovjaga 2017-11-10 15:17:41 UTC
Same behaviour already in 3.6.7, but not in 3.3.

Arch Linux 64-bit, KDE Plasma 5
Version: 6.0.0.0.alpha1+
Build ID: 1aba1955f161cc112dab80b6b3e78ec7761616fc
CPU threads: 8; OS: Linux 4.13; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on November 10th 2017

Arch Linux 64-bit
Version 3.6.7.2 (Build ID: e183d5b)

Arch Linux 64-bit
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 3 QA Administrators 2018-11-11 03:46:45 UTC Comment hidden (obsolete)
Comment 4 Roman Kuznetsov 2018-11-11 16:01:47 UTC
don't repro in

Version: 6.2.0.0.alpha1+ (x64)
Build ID: 0b2d153f58c83fb289c96b348631e44e553b1a9a
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2018-11-02_21:11:48
Locale: ru-RU (ru_RU); Calc: threaded

but may be is it only Linux problem?
Comment 5 Buovjaga 2018-11-11 18:19:03 UTC
I can repro on Win.
I don't know, if Roman understood: when clicking the filter for A in step 2, it should only show ✔07-2016 in the list. This is still the case in 3.3.0, but not in 3.5.0.

Version: 6.2.0.0.alpha1+ (x64)
Build ID: 317f5f2323b8ff7948c4812faaeb0c2a3b907ce8
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-11-07_02:31:39
Locale: fi-FI (fi_FI); Calc: threaded
Comment 6 QA Administrators 2019-11-12 03:32:59 UTC Comment hidden (obsolete)
Comment 7 b. 2020-05-19 16:52:18 UTC
30 months later ... 

hello @Kevin, 

you managed to have two overlapping data ranges in your file, 

one "workshop_consumption", manually set and covering A1:A3692, 

one "__Anonymous_Sheet_DB__0", such ranges / names are automatically created when you apply an autofilter to a 'not-predefined' range, covering A1:B3692, 

this was not 'foreseen' by the developers, and or too complex for a programmer to apply a non-conflicting handling for it, thus the two filters collide in a similar manner as if you apply one to column A and one to columen C, by sorting rows touching the other filters range they are in conflict, leftmost column wins?,  

i'm unsure if 'notabug, user error', or if one can request an error handling option against the construction of such situation ... 

your original definition: 

<table:database-range table:name="workshop_consumption" table:target-range-address="'Source Data'.A1:'Source Data'.A3692" table:orientation="column"/>

<table:database-range table:name="__Anonymous_Sheet_DB__0" table:target-range-address="'Source Data'.A1:'Source Data'.B3692" table:display-filter-buttons="true" table:orientation="column"/>

and it's not the first but a subsequent save of the file as you got - wrong - 'table-orientation' tags ...
Comment 8 Kevin Suo 2021-05-10 08:36:56 UTC
(In reply to b. from comment #7)
Sorry for the late reply.

Now I see that there is a self-defined database range in "Data - Define Range". Not sure when and how this was defined. Deleting that range would solved this problem.

Close as NOTABUG.