-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autofilter on the wrong Row when you have an header line #546
Comments
@rotda Thank you. I reproduced. I think that the original developer had in mind that a filter could be only at least two rows and consequently did an arbitrary fix to extend a one-row filter to two rows. Note that when the method To reproduce:
I don't see any side effect to do as you said. I would just delete the whole block from line 423 to 429 (as per your screenshot), and I would add a condition that if row_start > row_end, their values are switched e.g. if row_start = 6 and row_to = 2, we switch them to become row_start = 2 and row_to = 6 (technically speaking, in Excel, doing a filter from row 6 to row 2 works the same as a filter from row 2 to row 6, but I'd like to not allow it, maybe that would avoid future problems and at least we address/document explicitly the case in the program...). @AndreaBorgia-Abo What do you think? Thank you! |
@AndreaBorgia-Abo See my proposal in the PR. Thanks! 👍 |
@sandraros I should be able to do this tomorrow, will let you know. |
With Excel 2013 it seems to work as expected, however Libreoffice 7.1 won't show the autofilter when opening the file, both before and after the fix.... I've also tried to place column headings in row 1 but it makes no difference, weird. |
Hi ,
I use the template function of abap2xlsx but my excel have an header line and then the autfilter line.
In this case there is an bug in ZCL_EXCEL line 423 ( see screenshot) . It set the rowstart to 1 when row_start > = row_end. In my case then autfilter is on header row :-(
When I comment the line it works with out any problem
The text was updated successfully, but these errors were encountered: