Hopefully someone can help me with this - it's really driving me nuts.
A problem description follows the diagrams.

[Diagram 1 - logical grouping I want users to receive)
Accounts (ALL Level)
--Account#2
--AccountGrouping#1
--Account#4
--AcountGrouping#2
--Account#6
--Account#7
--Account#8

--Account#10
--AccountGrouping#3
--Account#12
--AccountGrouping#1
--Account#4

[Diagram 2 -Table Layout]


PKID AccountID Description ParentAccountID
1 1 Accounts
2 2 Trial Balance 1
3 3 Account#1 2
4 4 Account#2 2
5 5 AccountingGroup#1 2
6 6 AccountingGroup#2 2
7 7 Account#3 5
8 8 Account#4 5
9 9 Account#5 6
10 10 Account#6 6
11 11 Account#7 2
12 12 Account#8 2
13 13 BalanceSheet 1
14 14 Account#9 13
15 15 Account#10 13
16 16 AccountGrouping#3 13
17 17 Account#11 16
18 18 Account#12 16
19 5 AccountGrouping#1 16

Please note from diagram 1 that AccountingGroup#1, and subsequently
Account#3 and #4 are the SAME accounts that have a place in two
different rollup hierarchies.

Please note from diagram 2 that this is an "unbalanced (variable depth)
hierarchy" with an FK(ParentAccountID) to PK(AccountID) relationship
that defines the rollups. Also, please note that "AccountingGroup#1"
(AccountID=5) has a different PKID for table integrity, but the
AccountID is used to place the account group in multiple rollups.
Subsequently, it was my expectations that the accounts defined beneath
the group should come through with it.

Now for the problem - when I build the cube, the parent-child hierarchy
dimension will place AccountGrouping#1 (and its accounts) under trial
balance, but NOT under Balance sheet. I guess this is the case because
it was defined under Trial Balance first.

Anyway, I'm hoping there is someone else out there that has "shared"
attributes within a hierarchy and can tell me how to get this to work -
since my idea obviously does not work.

Thanks in advance

Ryan

What's happening is perfeclty normal.
Even if members with PKID 5 and 19 have the same name, they have different
key thus they are really two distinct differentmembers with their own value
and hierarchy.
Members with PKID 7 and 8 are set to rollup to member with PKID 5, not with
member 19.

Unfortunately in AS2005 we do not support the same member with two different
parent

"rhunt" wrote:

Analysis Services does not have true support for shared
members/attributes.

However, I did an article on my blog about a similar situation here:
http://geekswithblogs.net/darrengosb...les/57811.aspx

Have a look and see if it is of any help.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <1140720225.731378.323430 (AT) g47g2000cwa (DOT) googlegroups.com>,
rhunt01 (AT) hotmail (DOT) com says...