thank you very much for the answer.
Usually it's totally fine to put a hierarchy (country, region, city) and other attributes like operating system in one dimension. I do not really undestand the concept of the framework is using here.
So, if I would like to filter by an attribute which is not a member of a hierarchy I have to put it in an seperate dimension? This would mean that I would have about 200 dimensions. I dont think thats meaningful.
But if I would like to filter (cut) by an attribute which is not a member of an hierarchy it has to be a member of another dimension.
And just theoretically: If I create another hierarchy for the operating system with just one level I would not be able to group by operating system (drilldown=Country (real drilldown) and drilldown=operating system (grouping).
Furthermore if one dimension can just have items which are part of a hierarchy (I would need about 200 of then) in my cubesviewer filter and drilldown dropdown I would have a list of 200 items.
I'm not sure if I understood the concept of cubes right but I never had this problem in another BI tool.
-If there is a hierarchy in a dimension, can't there be attributes which are not part of the hierarchy?
-If I would like to drilldown by one hierarchy, I'm not able to group by an attribute which is part of the same dimension?
-Do I have to create a seperate dimension for all attributes which are not member of a hierarchy?
Thank you very much for your time