Hieracy recognizes any column under hieracy as the first column in hieracry list
-
Hello,
I have cubes where their folders are built from facts and dimension tables, and in the diagram, I use hierarchy to place columns under a hierarchy that I named. But, I have a single script that provides all the data , I guess a single table of fact and dimension if it were, that supplied one folder to the cube. And in that cube I go to the diagram and place columns into a named hierarchy to group, and it doesn't matter when I select a column in Excel, the first column in the hierarchy list will be the only one whose values display. Is this simply a limitation of the single folder of no differentiation of facts and dims? Thanks, JPQ
- quinn.jay - Friday, July 28, 2017 8:05 AM
This is rather unclear to me. Can you possibly include a few screenshots to help us understand what is happening and what you hope to achieve?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin - Phil Parkin - Friday, July 28, 2017 8:13 AM
-
When I create a hierarchy and drag the columns to it, and then build/deploy and connect with Excel, and then drag from the Geography folder of the hierarchy, and drag Cluster and drop in Columns, I get Region instead, and there is now way I can build the hierarchy in the cube and drag and drop within Excel connected to the cube to get any different result. So I'm wondering if this is a limitation of a single table holding aggregated data.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply