Apache OpenOffice (AOO) Bugzilla – Issue 96795
Applying an autofilter after a standard filter gets the filter criteria lost if a regexp has been used
Last modified: 2013-05-03 11:29:29 UTC
Current behaviour vi: - apply an autofilter on one column, then autofilter on another column => Ok (the second filter filters the results from the first one). - the same as before, then add a standard filter on a third column => Ok (the previous filters are kept in the standard filter interface). - apply standard filter on one column, then standard filter on another column (by adding a second criteria) => Ok (the second filter filters the results from the first one). - the same as before, then add an autofilter => applied standard filter gets lost. I have this behaviour whenever I use a "database area" or not. Expected behaviour: Applying autofilter and standard filter should not be sequence-dependent. That means that in whatever sequence they may be applied (autofilter then standard filter, standard filter then autofilter, ...), we should never lose the criteria that we set with the former filter method. I found a "quite the same" issue (but filters were applied in the reverse way): Issue 16766 (closed).
Sorry, this issue was posted due to a mishandling error, and wasn't complete at the moment at which it was posted... So I'll rewrite description (please consider the previous description as false).
Sorry, this issue was posted due to a mishandling error, and wasn't complete at the moment at which it was posted... So I rewrote the description below (please consider the previous descriptions as false). Current behaviour and problem description via a use case: - activate an autofilter - then add a standard filter (from the autofilter's drop down menu) and use a regexp to filter on the C column (for instance) => Ok (the filter is well applied) - then, from the autofilter's drop down menu, autofilter on another column (B column for instance) => PROBLEM : the previous standard filter we applied gets lost! I have this behaviour whether I use a "database area" or not. There's no problemn if we don't use a regexp (wildcards, etc.). I'll add a use case file... Expected behaviour: We should not lose the standard filter criteria. And in general, applying autofilter and standard filter should not be sequence-dependent. That means that in whatever sequence they may be applied (autofilter then standard filter, standard filter then autofilter, ...), we should never lose the criteria that we set with the former filter method. I found a "quite the same" issue (but filters were applied in the reverse way): Issue 16766 (closed).
Created attachment 58448 [details] testcase
Created attachment 58450 [details] screencopies for the servers.ods testcase
Indications for the "servers.ods" testcase file: 0 - for the screenshots, unzip the servers_screencopies.zip file: you'll find the 4 screenshost 1.png, 2.png, etc. 1 – Select the data range « Data_Range » (in the menu: Data > select the data range) 2 – Activate an Autofilter on this 3 – [screen copy: 1.png] Click on the drop down menu on the C column to apply a standard filter : we want to look for all brand names beginning with the H letter. So the field name is "Brand", the condition is "equal to" (or "="), and the value is "H.*" (without the " caracters). Don't forget to check the "generic wildcard" box in the Options. 4 - [screen copy: 2.png] The 4 results at this time... 5 – [screen copy: 3.png] Autoflter the B column on "UNIX" 6 - [screen copy: 4.png] Problem! You get 2 results (server5 and server8) instead of 1 (server8, which is the only one to be "UNIX" and "HP"). Why? Because the "beginning with the H letter" criteria was lost while applying the autofilter...
I can reproduce the problem.
As given in Comment 2 Rev. 1476029 Win 7