Showing posts with label dimension. Show all posts
Showing posts with label dimension. Show all posts

Friday, February 24, 2012

Drillthrough row count is less than [Measures].[Sales Count] from cube

The reason that this is happening is somewhat attributed to the fact that I have 2 different breakouts (2 attributes in the same Customer dimension) of customer territories and security is only set at one of the territory types.

(Security was set at both, but I was having the fore mentioned issue, so I trimmed the restriction down to one territory for only one territory type - hoping that any customers under that one territory type would also show up under their corresponding territory type 2)

Thinking about the mdx/drillthrough results in more detail, I'm leaning toward the mdx results being wrong and the drillthrough being right.

Is there something I can do to fix this or is it a bug?

I wish I could give more detail, but it's tough.Adventure Works didn't seem to have a similar setup because customer.geography isn't related to sales territory.group.

If I run the following sql query on the source data, 3 of the type2 territories are returned:

select Territory2Name, count(*)

from dimCustomer

where Territory1Name = 'East'

group by Territory2Name

One of the Territory2Names is 'Section 2'.Now in here, there's only a count of 1 customer, yet when I look at the cube for Section 2 and [Sales Count], there's easily more than 1 customer composing the total and if I look at a sales dollars, it's the same thing.When I do a drillthrough, then it's correct - results are only for that one customer.

Any thoughts on this perplexing problem?

Does your security role have the Visual Totals option ticked?

If not it will be showing the total for the "All" member of the Territory1 attribute unless you are also explicitly filtering by a Territory1 member.

|||Both of the dimension data security attributes had visual totals checked.

What I ended up doing to solve this problem is only giving access to an area in territory type1 and did not specify any security on territory type 2. This was exceptable for my case - users just needed access to a sampling of the items in both territory types, but in other cases, a person might have to do more digging to get access to a specific area from both geographical types..

Tuesday, February 14, 2012

Drilldown for Parent Attribute

Does anyone know how to create a drilldown matrix or table using a parent attribute in Analysis Services?

Currently, I have a dimension with this parent attribute which contains up to 10 levels. Then, if you click "Browse" in the Analysis Services toolbar it will let you expand each node until you reach the end of the branch. This allows a variable length tree. However, the problem is that when I go to add this attribute to my query in reporting services it only adds the first level. In other words, when you expand the attribute in the query designer, you can see all ten levels exist but only the first level is added to the report. I've also tried to manually add each level into the query, but this also fails. It ignores whatever level I add and just keeps the attribute's first level.

I know this is kind of a confusing problem, but I'd really appreciate any advice.

Thanks!!
Joel

Does anyone have any ideas or need more clarification?

Thanks

|||

Still stuck... Just wanted to get a few more looks at this problem.

Thanks