This content has been marked as final. Show 6 replies
By default a parent/child file will build the rollup with the first instance as the stored member then secondary instances as shared members. If it is not happening for you, I recommend looking at the dimension build properties in the load rule. I'll guess move shared members is checked. It you do not have a parent/child file then you can still build shared rollups. For example suppose you havea level based file and level 0 should be shared, then your file would have to look like
lev0, lev1,lev2,lev3,Lev1 (the shared parent), lev2
no, the move shared members is not checked here. I have a parent child file
Here is my issue (simplified greatly of course) And be aware that this is in an ASO cube
49999 (this is the child)
49999 (shared member)
I cannot get the file (which is just a comma delimited flat file with parent and child only) to load 49999 as a shared member in the Alternate without moving it from the Primary
You can check here if you are satisfying the conditions for creating shared members under the Hierarchy (refer to Alternate Hierarchies). Plz note that rules for shared members are different in ASO world.
Otherwise there is no reason why you should not be able to create a shared member.
I am able to create a hierarchy using a sample file like this ->
ENTITY (Multiple Hierarchies Enabled)
The rule file has only "Allow Property Changes" on.