Pilgrim_Paul
New Member
- Joined
- Oct 14, 2015
- Messages
- 5
- Office Version
- 2016
- Platform
- Windows
I have a question about the ColumnRange of a pivot table. I was unable to find a single reference to ColumnRange anywhere in the InformIT online version of MrExcel's Excel 2016 Pivot Table Data Crunching, far and away the best pivot table reference in print.
I am struggling to phrase the question so you easily know what I am asking. Here goes:
It appears to me that if one specifies a ColumnRange (to form buckets for categorizing the transaction data), that feature overwhelms any previous specs in the Values area. That is, ALL data is then categorized into those buckets. There is no possibility of having additional leftside or rightside columns summarizing data unrelated to the buckets. "You want buckets? You get buckets (and subtotals)! But that's all you get."
Is my surmise accurate or am I missing some GUI action to get what I want?
If I am correct, it appears to severely limit the usefulness of ColumnRange (which is already hindered by the dynamic nature of the report width due to reduced columns if data is filtered). Ex: One guy sells all 8 different SKUs, but another guy specializes in just 5.
Considering these limitations, we are forced to add a bunch of helper columns to the data source to create and manage our own buckets.
"Say it ain't so, Joe."
I am struggling to phrase the question so you easily know what I am asking. Here goes:
It appears to me that if one specifies a ColumnRange (to form buckets for categorizing the transaction data), that feature overwhelms any previous specs in the Values area. That is, ALL data is then categorized into those buckets. There is no possibility of having additional leftside or rightside columns summarizing data unrelated to the buckets. "You want buckets? You get buckets (and subtotals)! But that's all you get."
Is my surmise accurate or am I missing some GUI action to get what I want?
If I am correct, it appears to severely limit the usefulness of ColumnRange (which is already hindered by the dynamic nature of the report width due to reduced columns if data is filtered). Ex: One guy sells all 8 different SKUs, but another guy specializes in just 5.
Considering these limitations, we are forced to add a bunch of helper columns to the data source to create and manage our own buckets.
"Say it ain't so, Joe."