SSAS Cube Filter Not Working

Hello Experts,
I am a noob to SSAS.  I have inherited a cube that was created by one of our other developers.  Unfortunately, he was let go in a recent round of layoffs.  What is happening is that one of our users wants to filter for a particular order number and then filter on a column called 'Usage' which contains only 3 values - Money, Bonus and Filler.  Bonus and Filler are always zero dollar spots (we sell commercial air time on cable TV channels), so the Average Unit Rate and Net Revenue should be zero.

I have attached a couple of screen shots to show the results from the cube and also a query that I put together that uses the same views that are used in the data source view and joined in the same way as is defined in the cube.  In the query you can see that there are many Bonus spots for line 010 and also that line 098 has a Usage type of Money.  However, the cube displays only one spot from line 010 and for some reason also displays line 098.

Based on the fact that the query seems to show the correct data, I think the problem must have something to do with how the cube is setup.  But as I said, I am a noob to SSAS so I have no idea where to start looking.

Any help is appreciated!
Thanks.
Cube.JPG
Query.JPG
LVL 5
adlink_laAsked:
Who is Participating?
 
agandauConnect With a Mentor Commented:
If the user is only interested in usage of "Money" you can modify the DSV so that the only "money" records come in.

I would think having all the records would be better for analysis, in which case you need a usage dimension.  

Add a named query to the DSV called perhaps "Usage".  It can just be "SELECT DISTINCT Usage FROM BoardReports_Performance", or if that would be an excessively long running query then somethine like

SELECT "Money" as Usage, 1 as UsageSortKey
UNION
SELECT "Bonus" as Usage, 2 as UsageSortKey
UNION
SELECT "Filler" as Usage, 3 as UsageSortKey

Draw a relationship between this table and the fact table on the Usage column so that the arrow is pointing to the Usage Colulmn in your new Usage table.

In BIDS, create a new dimension based on this table (if this is sounding confusing, there are walkthroughs on MSDN).  Bring both columns in as dimension attributes making sure that "Usage" is the key.  Set the UsageSortKey to visible = false.  For the attribute "Usage", the "Usage" column will be both the Member Name and Member Key, and you can set the sorting for the "Usage" attribute to sort by Attribute Key and then point use the UsageSortKey.

Add this dimension to the cube, and double check that the "Dimension Usage" (too many usages!) shows the relationship between your fact Measure group (fact table) and the new dimension is set to a regular relationship on the column "Usage".

Reprocess your cube.  Then in Excel, you can use the usage tab either in your rows or columns or as a filter.
0
 
adlink_laAuthor Commented:
Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.