PRB: The Ordering of a Member in a Ragged Hierarchy May Not Be Correct (326586)
The information in this article applies to:
- Microsoft SQL Server 2000 Analysis Services
- Microsoft SQL Server OLAP Services 7.0
This article was previously published under Q326586 SYMPTOMS
When you browse a cube or a dimension in Analysis Manager, the member may not be ordered as you specified in a Ragged Hierarchy.
The Order By property of the properties pane in Dimension Editor determines the sort order for displayed members. You can sort by member name, member key, or any member property that is defined for the level.
CAUSE
This behavior may occur if you are using the Hide Member If property to create a Ragged Hierarchy in a dimension.
This behavior is by design.MORE INFORMATION
If you use the Hide Member If property to create a Ragged or Unbalanced Hierarchy, and if the member under the current level is hidden, the descendent member from the next level (if one exists) moves up and appears under Analysis Manager. Even the members from the current level and the descendent members appear at the same level, but the members from the current level are ordered first, and then the descendent members are ordered.
| Modification Type: | Major | Last Reviewed: | 6/25/2004 |
|---|
| Keywords: | kbnofix kbprb KB326586 |
|---|
|