Saturday, March 02, 2013 8:15 AM
I have a problem in cube, it shows the same CustomerCatgoryName for different CustomerCategoryCodes. The Customer Dimension table has correct data, with different codes having different names, but not sure why the cube shows same name across all.
Can you please help me to find the root cause for this, seems something related to underlying data, but not sure what can make the cube behave this way.
Sunday, March 03, 2013 4:57 AM
Do let me know if any more details are required.
Monday, March 04, 2013 6:32 AMModerator
Monday, March 04, 2013 11:03 AM
we have options like the value column and the name column in the dimension properties try to use them in order to solve your problem.
please let me know still your facing the issue
Monday, March 04, 2013 12:36 PM
I would recommend you to check the namecolumn property, as that decides what is being displayed to the end user?
Also, the key column property determines its uniqueness..Did you get any processing errors like duplicate entries, when you process the cube?
Tuesday, March 05, 2013 5:36 AM
Just to give some more details:
1. I don't get any error while cube processing.
Data in the customer dimension table:
Data shown in the cubes:
So in cube i see same name for different codes, even though in db i have the correct values.
3. There exists a Natural Hierarchy between the below filed and we have an attribute relationship defined ( below example is for Codes, same exists for Names).
Top to Bottom Hierarchy:
I have few cases where same CustomerCode has multiple OutletCodes, not sure if this can create issues. As in another db its the same but all works fine there.
Hope this gives much insight into the issue. Any quick help would be much appreciated, with a possible work around ( if changing the design is the only solution).
Thursday, March 07, 2013 10:04 AM
Hi Vinish ,
Could it be you're dealing with Many-To-Many issue between the hierarchy levels ?
I hope the next links will give you an idea :)
Regards, David .
Thursday, March 07, 2013 2:23 PMIn your DSV, are you referencing the dimension table directly, or a database view? If it's a database view, I'd suggest looking there to see what data is actually being returned from the query.