July 4, 2005 at 1:39 am
Hello Colleagues,
In order to circumvent the maximum limit of 64,000 members per level, I created Member groups for that level following the guideliens in Books Online.
But one problem is that while setting the Grouping property to "Automatic" in the new level it automatically changes the data type for Key Column to INTEGER whereas for the original level it is CHAR(16).
And also INTEGER data type cannot be changed back to CHAR(16), it gives the message "Cannot Set".
Now while processing the cube I get the error message,
"Dimension Member Key Is Not Unique" although Member Key Column and Member Key Name for original level are set to TRUE.
Can anybody help me in this plz.
Thanks.
July 4, 2005 at 6:07 pm
Hi Ansari,
How did you add the grouping level? I did a quick test using the foodmart sample and the data type wasn't changed by making the grouping automatic?? Basic reproduction steps (for foodmart) are:
1. Create new dim using Editor
2. Select the Product table as source
3. double click Product Name to add it as a level
4. double click Product Name to add it as another level (comes in as Product 1)
5. Rename Product (should be the highe of the two levels) to 'Product Groupings'
6. Rename Product1 to 'Products'
7. Change the Grouping on the 'Product Groupings' level to Automatic, this fire the dialong indicating that AS will make uniqueness changes for you, click OK.
8. Save and process the dimension.
Just out of interest, if the 'Member Names Unique' property for the lower level is set to True (as per your post) and your data does actually contain duplicate names, this will through the error you're seeing. Hav you done a quick 'group by' with a count (ie a TSQL query) to ensure that your names are indeed unique?
Steve.
July 5, 2005 at 2:09 am
Hi Steve,
Thanks very much for the efforts.
Yes, my data does have the duplicate names.
Let me explain it.
We have a Client say 'O', this client will have business partners 'P1', 'P2','P3' and so on. Each of these 'P1', 'P2' etc. will have the customers 'C1', 'C2', 'C3' and so on.
There may be a case where these business partners will have common customers say 'C1' and thus 'C1' will be repeating. And this is the level where I'm trying to create Member Groups.
I suppose it is taken care by AS when we set the Grouping to Automatic.
I double checked and still it is changing the data type from CHAR(16) to INTEGER when I'm trying to create Member Groups for a level under private Dimension.
Still I am struggling to resolve it.
Thanks.
July 5, 2005 at 6:43 pm
Can you post the details on your dimension? i.e. How many levels. What the source is for each level (e.g. Business partner or Business Partners Customer etc etc).
To confirm, you've added an *additional* level to hold the grouping? you're not trying to make the grouping exist int he level you want to view within the cube? I.E. When you use autogroupings, this level is transparent to the end user. The example below is a dimension name, then level names with their types.
My Customer Dim
Business_Partners_Grouping -> created by dragging the business partner ID in to dim. Set grouping to auto
Business_Partners -> created by dragging the business partner ID in to dim (no grouping set)
Bus_Part_Cust -> created by draggin the business partner cust ID field in to dim (no grouping set)
The above example will work for you if you have >64k business partners.
Steve.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply