https://bugs.documentfoundation.org/show_bug.cgi?id=173827
--- Comment #15 from ady <[email protected]> --- (In reply to Octavio Alvarez from comment #14) > You are missing the point. *AutoFilter IS the issue*. I says so in the > report, I says so in the subject for the report. No. The real problem is not AutoFilter. By carefully reading comments in this report, I am not the only one with this opinion. > > Everything you claim I didn't say, it is said in the initial submission. > > The very first paragraph of this report's description clearly states what > you claim I didn't say: > > > When data is imported from a database, a range is automatically defined > > without user's knowledge. > > This is *the context* of the issue but this is *not* the issue! Importing > data is not mentioned in the *steps* because *there is no need* to import > data to replicate the issue, just to create a database range. But the > context *is described*. I disagree. The STR should rather provide a way to reproduce the problem itself, not just a generic use-case in which the main problem occurs. That's why you think that AutoFilter is the problem, instead of focusing on the result of importing the data (in a specific way). By focusing on the use-case (i.e. AutoFilter behavior) rather than the main problem (i.e. how to effectively filter imported data from a database when calculated columns are added in Calc), you are not making the report easier to solve. Moreover, if you are going to manually add a calculation column that should also be part of a data named range (for whichever reason), then I don't really know how you would expect the named range to know in advance what the area should be. And that's why you think that AutoFilter is wrong, but it isn't. AutoFilter is acting on the whole "table", and your "table" does not include the calculated column by default. > > The issue is *AutoFilter*, as I already said, and as the subject says. > AutoFilter (or its documentation) is the issue because it behaves in direct > contradiction to what the help text says. Again, from comment 10, the help > says: > > > When no cell range is selected, the AutoFilter will apply to the column up > > to the first empty cell. Please ensure that you select the appropriate > > range before applying the AutoFilter. AutoFilter behaves exactly like that. > > This is not true as it is stated, because a database range is considered > before all this. And it says that selecting an appropriate range (cell > range, from context) *will* create an expected AutoFilter, not 2 > AutoFilters, not independent AutoFilters. > > And the Guide says: > > > It is possible to add AutoFilters to individual columns by selecting those > > columns before choosing Data > AutoFilter, clicking the AutoFilter icon, or > > pressing Ctrl+Shift+L, but this is not normally necessary for a database > > table. Again, it behaves exactly like that. The additional column is not part of your "table". You manually add a column, then you should also modify the named range (or rather add a new named range) for a "table" to include that column. The calculation column is not part of the "table" by default on its own. > > Even if it were correctly documented as to the current behavior, there is > room for improvement: just select the range to AutoFilter, apply, and we > should get one single AutoFilter in which all columns can combine instead of > independent AutoFilters. Your suggestion has negative consequences too, as the example I already provided in prior comments. Perhaps there is a different method to obtain the desired result. Perhaps a Standard Filter (not from AutoFilter but from its own menu entry) is a better match for your use-case. I would suggest to be open to a different way of getting the result you want, instead of focusing on AutoFilter. Asking in an open way ("How could I get this result from an imported database?") instead of imposing the way you currently import the data or which method you think is the best in order to filter the data (which might not be AutoFilter) might be better in order to improve the situation. Other users at <https://ask.libreoffice.org> might help, if the question is presented in an open way, aimed at the real goal (instead of limiting yourself (and others) in the way you think the goal should be obtained). -- You are receiving this mail because: You are the assignee for the bug.
