Strange dimension hierarchy problem! - sergei.sheini |
09-May-08 07:42:29
|
Hello,
We have something like the following table in our database:
ProductID | ProductName | Level1Name | Level2Name | Level3Name
Two dimensions need to be made of this table:
1. "Product": ProductID as key + ProductName as name - no problem
here.
2. (here is the problem!!!) Hierarchy of levels so that it's displayed
as the following:
-L1: A
--L2: A.1
---L3: A.1.1
--L2: A.2
---L3: A.2.1
---L3: A.2.2
--L2: A.3
---L3: A.3.1
---L3: A.3.2
---L3: A.3.3
-L1: B
--L2: B.1
---L3: B.1
---L3: B.2
and so on...
It works like this on SQL Server 2000. Now I'm trying to create the
same thing on 2005, but I get this strangest problem where only ONE
CHILD per level is displayed on the Browser tab (both in dimension and
cube). So the above would something like this:
-L1: A
--L2: A.2
---L3: A.2.1
-L1: B
--L2: B.1
---L3: B.1
It's as if OLAP arbitrarily (and randomly) throws out entries from the
dimension. It always shows only one child per each level, although all
entries in the database table are processed (when I use this dimension
in cube, measure values do not tarnish).
The Dimension Structure looks as following:
Attributes tab:
-(key)Products
Level1 Name
Level2 Name
Level3 Name
-Level1 Name
Level2 Name
Level3 Name
-Level2 Name
Level3 Name
-Level3 Name
Hierarchy tab:
-Level1 Name
Level2 Name
Level3 Name
-Level2 Name
Level3 Name
-Level3 Name
Can anyone help? Maybe it's some parameter that I'm missing.
Thanks!
S. |
 |
| |
|
|
| |
Strange dimension hierarchy problem! - sergei.sheini |
09-May-08 07:42:30
|
hi, i think i solved it. haha. i needed to have this in the Dimension
Structure:
Attributes tab:
-(key)Products
Level1 Name
Level2 Name
Level3 Name
-Level1 Name
-Level2 Name
-Level3 Name
Hierarchy tab:
-Level1 Name
-Level2 Name
-Level3 Name
s. |
 |
| |
|
|