so, if you have WorkType dimension, you should put the
"{[WorkType].[CU]} On Rows" and so you will get on your result cellset rows that data grouped by WorkType Issahar
senior software engineer
Hi, Sam.
In my previous Message I gave you a wrong answer.
So, Excuse me.
Now...
If the JobId is a dimension in your OLAP databse
I think (but I am not sure) that you cannot do this because the WorkType
dimension (or level) is not the same hierarchy with your JobID dimension so you cannot slice WorkType dimension by another dimension that has not any parent/Child relationship to it - (actually I think that you cannot slice one dimension by another at all but there are some tricks...)
if you have JobID dimension, but if not - I don't see possibility to group something in OLAP by value that is not member of some dimension..
May be you can think about using Mining Models in Olap 2000 but I have no experience in this and I don't know how to do that..
If the resolution of this problem is very critic for you managers, you can think about creating a little realtime cube sliced by JobID dimension (make this dimension a ROLAP one because as I guess, the number of JobID can be huge???) and by WorkType dimension and as measure select the count of WorkType (count of Works?)...
Sorry If I confused you.
If you will find the right solution for this, please, notify me it will be very interesting to know...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.