Non-empty clause causes wrong member selection behavior.

[mysticfall]

This is reported by Vahe in the mailing list :

• https://groups.google.com/d/msg/pivot4j-list/TYBeTHK6N0s/idb5tcLsvy0J

  Steps to reproduce

  1. Select cube "Sales"
  2. Create pivot table with "promotions" ,"stores size in sqft" , "measures.unit sales" in columns(order top to bottom), "Store type" in rows
  3. Choose "Non empty" from bottom toolbar
  4. Click on Hierarchy Configuration for "Promotions" node. Add only "Best Savings" and keep All
  5. Expand "BestSavings"->"All Store size in sqft". You can see #null,21215,23598,23688 members for "Store size in sqft"
  6. Click on Hierarchy Configuration for "Store size in sqft" . You can see only #null,21215,23598,23688 members in Selected Members part. Close without changes.
  7. Click on Hierarchy Configuration for "Promotions". Add all items. Click "OK"
  8. In pivot table under "All Promotions" you can see "All Store size in SQFTS", #null,21215,23598,23688 members. (This is the problem) Please note that we do not change any hierarchy configuration for "All Store size in SQFTS", but it does not show all available members.
  9. We can make sure that there should be other members as well when doing Collape and Expand "All store size in sqfts" under "All promotions". Now you can see much more members for "All store size in sqfts".

[mysticfall]

We can check if all existing ExpNode children of a hierarchy is either an 'all' member or a '.Chindren' function call. However, there's no easy way to find it out as initially, the Quax only keeps the position tree without FunCall nodes.

[mysticfall]

Possible approach to solve this one (not working yet) :

• https://gist.github.com/mysticfall/4e7eba3f129c49152669