https://bugs.documentfoundation.org/show_bug.cgi?id=152658
--- Comment #3 from Colin <that.man.co...@gmail.com> --- (In reply to m.a.riosv from comment #2) > Sorry, but what is the criteria to get 75 selected? What is the criteria for deselecting it? If I add a line to the bottom of the array it's automatically included in both Excel and LO. If I set an Excel sheet in exactly the same manner as I did this LO sheet then Excel doesn't deselect the entry when it's edited. It is automatically included because there has been no exclusion by the user - I repeat NO exclusion by the user. > You are selecting from a list, why it should be re-selected after the change? NO, perhaps my description didn't make it clear - I made a change to an existing entry and then examined the list for other aspects and the moment I exited, LO decided of it's own volition to ignore the value because LO of it's own volition decided to deselect that new value. Excel doesn't deselect the value of it's own volition - that is the users' prerogative. I also believe that this is a NEW "feature" because I have spent two years performing the operation of amending values and hiding nulls but only recently has it started hiding real values. Initially, I thought perhaps it was me and my memory but then I performed the same task on Excel and discovered that it wasn't me going crazy, it is LO misbehaving. > The standard filter can do it, and seems to me, it works fine. > With 'Field name' 'D' '=' 'Not empty' Why would I need to play with standard filters to remedy a rogue action by LO? The slicer allows me to specify if I wish to exclude any or many items and include or exclude empty, null or zero cell values. What the slicer should not do is make those choices on behalf of the user. If I have a list of items where the value may change and I don't wish to see the ones that have reduced to zero I can exclude zero values when I filter. What should NEVER happen is that if I reduce the number then it is completely removed even though it has a value. Go shopping with 500 Euros in your wallet. Buy a shirt for 50 Euros pay for it. Look in your wallet at the next shop and discover your wallet has decided you no longer have the remaining 450 Euros. Is that how LO is supposed to work`? RE-READ the first line. If the autofilter is not set to exclude blanks it ditches the 74 and retains the selection of 75 - and that value remains in the subtotal regardless of how many times I examine the filter or deselect 225 or 450 or 62357,25 OR how many times I adjust the other slicers which only exclude entries from the same row -- You are receiving this mail because: You are the assignee for the bug.
