Page 1 of 1

How to load data to uneven hierarchy

Posted: Mon Jul 04, 2011 10:54 am
by binu.jose
Hi

I am trying to create a dimension with below hierarchy. But I am getting circular reference issue. Could you please help me to resolve this issue.

For example

Code: Select all

All Product
   ProductA1
         ProductA1
         Product A2
   ProductB1
         ProductB1
Admin Note: Moved from the Bugs forum. This is NOT a bug.

Re: How to load data to uneven heirarchy

Posted: Mon Jul 04, 2011 12:11 pm
by Alan Kirk
binu.jose wrote:Hi

I am trying to create a dimension with below heirarchy. But I am getting circular reference issue. Could you please help me to resolve this issue.

For example

Code: Select all

All Product
   ProductA1
         ProductA1
         Product A2
   ProductB1
         ProductB1
You can't have an element as a child of itself. In this case you have ProductA1 and ProductB1 as both children of a consolidation, and as the consolidation itself. You need to use different names for the consolidation elements.

Re: How to load data to uneven hierarchy

Posted: Mon Jul 04, 2011 1:29 pm
by binu.jose
Thanks for your reply.

I am able to create hierarchy .
I refered below URL to create hierachy. dimension is created with out any error. but i am facing some issue while loading data.


http://publib.boulder.ibm.com/infocente ... _Wksh.html

Re: How to load data to uneven hierarchy

Posted: Mon Jul 04, 2011 3:56 pm
by David Usherwood
And your issue is....?

Re: How to load data to uneven hierarchy

Posted: Mon Jul 04, 2011 9:26 pm
by Alan Kirk
binu.jose wrote:Thanks for your reply.

I am able to create hierarchy .
Not the hierarchy that you had in your original post you aren't. That simply wouldn't work. Never has, never will.
binu.jose wrote:I refered below URL to create hierachy. dimension is created with out any error. but i am facing some issue while loading data.
You're unlikely to be getting a circular reference issue when you're loading data. When you're creating metadata it's more likely and is usually caused by the sort of example you had in that first post. Either
(a) That you're trying to assign an element as a child of itself as you claimed you were; or
(b) That you're trying to assign A as a child of consolidated element B and also B as a child of consolidated element A.

But as the Request For Assistance Guidelines say:
Similarly if you're getting unexpected results, specifics of what you're running, how, and what results you're getting will yield a more valuable response than "I'm running a T.I. but my code doesn't work properly"
This would include the specific TI code which is generating the error.