I am going to +1 this. I haven't found anything out there except to duplicate the data field, and that causes a lot of problems!
If you duplicate the fields, then you can use the copies in a different hierarchy.
The problem is that it causes aggregate calculations to screw up. For instance, lets say I have the following:
If I want to make hierarchies of the following fields:
State > Gender > Cost
URL > Gender > Cost
Gender > Cost
I would have top have duplicates of the Gender and Cost twice. But if I am looking for the Aggregate of cost, it messes up the calculations.
Got a packaged workbook?
No, I don't have a packaged workbook. (Can't, it is sensitive data)
But my layout is the very same thing that I showed to you. If I have those fields, I have to make either duplicates of the data or a calculated field, both of which cause the data to get all skewed.
Just so we are absolutely clear about this, I have confirmed that the data sources that I am using has the same data.
I guess one solution is to have a data source per worksheet, that way I can have a unique hierarchy for each one, but that seems very wasteful.
A solution would be greatly appreciated, especially for something that would seem to be a very simple problem (that isn't apparently)
Mike create your situation using SuperStore dataset that came with Tableau. Just rename the fields to your field names and setup the viz the way you want, and show how your aggregates are getting messed up.
While that is a workaround solution, in complex dashboards like my own, it creates unnecessary complexity.
The copies are also required to have their own names, so you begin to create a big unmanageable mess when working with data of a certain complexity.
In my dashboards I have various hierarchies and I end up having to use a convoluted name-spacing scheme to control the additional complexity introduced by these identical copies.
It seems to me that a hierarchy should simply be an array of ordered references to existing fields. As a software developer, I understand that this may be easy to say, but hard to accomplish as there is probably a bunch of core implementation that assumes sole ownership of the field.
However, that said, removing this limitation would sure make my life easier as well.
+1 just bumped into this issue myself. I suppose I will have to duplicate my data source.
+1, I have the same issue. Duplicate dimensions have different names.
Duplicating dimensions for multiple hierarchies is not a neat work around I think. It is messing up the hierarchies. For some reason it's picking up the hierarchy that is 1st, alphabetically, in the dimensions pane even though I try to add the other hierarchy to the sheet. Would appreciate if anyone has a good solution for this.