[Libreoffice-ux-advise] [Bug 149984] Add sortable counts to AutoFilter drop down

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=149984

--- Comment #4 from Pierre Fortin <pf at pfortin.com> ---
I'm not seeing how a pivot table is going to help me...  

My sheets, on average, consist of millions of rows of text data; no numeric
fields to add or compute.  The AutoFilter lets me select categories within
columns such as city, gender, age, street, whatever...  With those selections,
the raw data on the filtered rows is all I want/need to see.  Having totals on
the AutoFilter per unique value would help decide if it's even worth drilling
down into certain values. 

In a multi-million row sheet, most columns have small sets of unique values:
State: 1, Moved-To: ~50, Moved-From: ~50, gender(sex): 3, County: 100,
UniqueID: rows-1, etc...   The number of rows based on the filters is in the
Status Bar (N of M records found) is of interest; but it's the raw data (all
columns) that we want to see; not some summary.  Our "summary" is the set of
visible rows.

Unless the pivot table rules have changed, our data violates the first rule of
pivot tables: lots of empty cells.  In some fields, it's important to select
rows which have empty cells in specific columns; such as large building tenants
without unit numbers...

I'm open to seeing if pivot tables are useful here; but it seems like lots of
wasted user time when a quick glance at a filter's list of values often tells a
story at a glance, as in:  "Whoa! Something's not right here... there are too
{many,few} whatevers in this set... Let's look at this [set of] value(s)..."

The goal is simply filtered views of entire rows; not sales numbers, etc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.