EVDRE u0096 Column Keys staying hidden on multiple expansions

Question

I have an EVDRE that has two membersets and two Column Key Ranges.  I also have the Hide Column Key option selected.  When the first expansion member list either increases or decreases upon re-expand and the original second Column Key Range stays hidden.
Before Expansion
PageKeyRange    sheet1!C4:sheet1!C20
RowKeyRange     sheet1!T33:V64,sheet1!T73:V85
ColumnKeyRange  sheet1!W28:IV32,sheet1!W69:IV72
After Expansion
PageKeyRange    sheet1!C4:sheet1!C20
RowKeyRange     sheet1!T33:V107,sheet1!T116:V128
ColumnKeyRange   sheet1!W28:IV32,sheet1!W112:IV115
The second column key range is below the first data range.  When members are added or removed from the first memberlist, the original second column key range's rows W69:IV72 remain hidden and the new second column key range's rows W112:IV115 are also hidden.  Except now the original column key rows now contain data not column keys.
I need to know how to make the original second Column Key Range unhide with every re-expansion.

Answer 1

If I understand the issue you have written, the following information may assist you in a solution.
How the key of a cell is built
The full key (“current view”) of a cell is ultimately controlled by EvDRE “overlaying” onto each cell the definitions of a current view as defined by any combination of the following settings:
1)     The system current view, as defined in the Current View bar
2)     The workbook current view, as “parked” in the workbook options, if set.
3)     The page current view, as defined in the PageKeyRange, if existing.
4)     The column current view, as defined in the ColumnKeyRange
5)      The row current view, as defined in the RowKeyRange
6)     The cell current view, as defined in the CellKeyRange
These definitions, if in conflict, take precedence from the lowest to the highest in the above list (The cell key, if existing, wins on the row key, that wins on the column key, that wins on the page key, etc.).
So, I think that if you keep the column key range of the 2nd set on the same rows as the 1st set as a relative reference, you should have a positive result, since the 2nd set of ranges create the point of intersection data retrival.  Otherwise, you may need to consider using 2 evdre statements.  If fact, if the data from the columns is in different catgories, or time members, you may want to consider this approach to develop a faster query.