Essbase Studio, ASO Multiple Hierarchies, and Recursive Dimensions

My first ASO cube, so bear with me please. And I have read the fine but sparse manual which does not directly address my issue as far as I can see. I see it discussed in Glenn's fine book also, but not specifically in terms of how to satisfy ASO requirements. Perhaps recursive tables are not the norm?

I am building a dimension that has multiple alternate shared member rollups. I have directed studio to build this dimension as Multiple-hierarchy enabled.

The table for this dimension is in parent/child form and includes both the stored and the shared (dynamic) rollups. Studio is failing to build the outline as it apparently wants to build all of the hierarchies as stored. I saw the hint about properties on Generation 2 members. I tried changing it from Store to Dynamic but that did not help.

Am I going to have to separate the stored hierarchy and the share hierarchies into 2 different tables or 2 different dimensions in Studio to get this to build?

CALVIN: You know, Hobbes, some days even my lucky rocketship underpants don’t help.