Home Dashboard Directory Help
Search

Creating a calculated member in a parent/child dimension breaks GetSchemaDataSet() for Members by Colin8098207


Status: 

Active


2
0
Sign in
to vote
Type: Bug
ID: 779808
Opened: 2/22/2013 9:03:47 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

If you have a dimension with a parent child dimension, you can use the "Create Member" syntax to add a member to it.

Having done this, if you attempt to retrieve members of the top level using GetSchemaDataSet() you get an exception.

Tried this with SQL2012 and SQL2012SP1.

On previous versions the metadata was returned without a problem.
Details
Sign in to post a comment.
Posted by Microsoft on 4/19/2013 at 11:40 AM
Thanks for filing this issue. We will consider addressing this in some future release of Analysis Services. In the interim, if this is critical for your workload, and you feel you need a hotfix for this issue, please file a case with customer support.

Thanks,
Analysis Services Product Team
Posted by Colin8098207 on 2/22/2013 at 9:32 AM
Oops, went a bit mad with the attachments there. One is a cube backup, the other is a C# project.
Posted by Colin8098207 on 2/22/2013 at 9:22 AM
Forgot to mention, this only seems to happen if the calculated member is at the top level, if it goes under another member it seems okay.
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
TestParentChildHierarchies.zip 2/22/2013 34 KB
ParentChildTesting.zip 2/22/2013 20 KB
ParentChildTesting.zip 2/22/2013 20 KB