![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
There is a measure in the cube called Price. Also a dimension called Product. I need to create a Dimension that classifies each Product by a "Price Range". For example, Expensive, Moderate, Cheap. A user can therefore choose Cheap from "Price Range" dimension and see the "Cheap" Products and the associated Measures (Price, Units Sold, Cost, etc). To derive the classification, a Case statement can be used CASE price WHEN price > 20.00 THEN 'Expensive' WHEN price BETWEEN 10.00 AND 19.99 THEN 'Moderate' WHEN price < 10.00 THEN 'Inexpensive' etc....... But I can't figure out how to make this information a dimension. I've tried a couple of things but have been unsuccessful. Please help! |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
Product is uniquely identified. There is not a specific error message, per se. I tried to create a virtual dimension based on the Price measure, but it won't allow a dimension to be based on a measure. It also won't allow a dimension to be based on the fact table. Also, there is more than just a Product dimension, that was just for illustration. There would be a customer dimension, a channel dimension, etc. The "Price Range" would apply to the intersection across all dimensions. *** Sent via Developersdex http://www.developersdex.com *** |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
This is true - Price is not an additive measure. This does not reflect my actual data. I gave this example for simplicity sake since my data is very industry specific. I was hoping not to have to change the star. That will mean the relational db team will have to get a request, spec it, blah blah blah.... It just seems like this should be something that is possible. The other two major OLAP vendors include this type of functionality.... it prevents the source data from having to be reworked. |
#7
| |||
| |||
|
#8
| |||
| |||
|
|
I just noticed your reply. Thank you for taking the time to respond... I figured out how to do this in AS 2000.... I created a Dimension using a measure field as a source, used an expression to convert the measure to a string using the Case statement above, used grouping and unique names, and voila --- it worked. I think the key is the Unique Member Names and Member Key. I had to create the dimension using the wizard, I couldn't get it to work using the dimension editor... but it was probably my own fault. Overall, however, I think your solution is the better one. |
![]() |
| Thread Tools | |
| Display Modes | |
| |