cancel
Showing results for 
Search instead for 
Did you mean: 

Hierarchy - Internal Leafs

Former Member
0 Kudos

Hi All,

I've got a data modelling question. Imagine a hierarchy of the following kind:

Organization A

- Sub-Organization A1

- Sub-Organization A2

Organization B

Now when I have a lookup into this hierarchy table I can only select the SubOrg's and Organization B, but not Organization A.

How do I accomplish to have every node being selectable in the lookup? Am I supposed to use internal leafs? What is the standard way to do it?

Thanks and Regards,

Ingo

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Ingo,

The use of internal leaf node as per reference guide is as follows:

For proper organization of the records within an MDM

repository, a hierarchy lookup field can normally be assigned only to the

value of a leaf node in the hierarchy.

Sometimes, however, remote systems may have records with inner

node assignments, in which the lookup field is assigned to the value of

an internal (i.e. non-leaf) node. Moreover, you may wish to preserve

these inner node assignments during inbound processing of records

and/or to create inner nodes and assign records to them during data

editing, for subsequent syndication of records having inner node

assignments back to the remote system.

MDM supports inner node assignments indirectly u2013 while preserving the

rule that a hierarchy lookup field be assigned only to a leaf node in the

hierarchy u2013 using an internal leaf node, a special type of leaf node that

represents the internal parent node immediately above it.

You can then make inner node assignments to the parent by assigning

records to the internal leaf u2013 which acts as a proxy for the parent for

assignment purposes u2013 just as you would assign records to any other

leaf node.

I hope this solves your query.

Regards,

Kaushik Koli.

Former Member
0 Kudos

data manager ref guide, sure..

Solved, thanks a lot!

Ingo

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Ingo,

Yes, this is how, it happens in MDM.

If you are having a node which has some child nodes in it then you can select only child nodes (Leaf Nodes).

Or if you are having a node which doesn't have any child then only you can select this node(again this is so called leaf node).

you can select only leaf nodes in the Hierarchy.

I hope this will clear your doubt.

TNR,

Saurabh...

Former Member
0 Kudos

Hello Saurabh,

The behavior you described is the reason for this post, no doubts

My question is whether internal leafs are the recommended solution for this.

Thanks,

Ingo

Former Member
0 Kudos

Hi Ingo,

I would like to suggest you some thing.

If possible create one Parent node named Organization Chart or some valid name and this will be the root node then you can select the Organization A because Organization A will then become the child of root node Organization Chart.

Regards,

Jitesh Talreja

Former Member
0 Kudos

Hello,

Thanks for your suggestion.

But Organization A has childs as well. For this reason it's not selectable even if it is a child of "Organization Structure".

Organization Structure

- Organization A

- Organization A1

- Organization B

In this example you can select Organization A1 and Organization B, but not Organization A.

But: You can select Organization A indirectly if you add an internal leaf. My question is: Is the usage of internal leafs recommended/standard?

Thanks,

Ingo

Former Member
0 Kudos

Hello Ingo,

As per my knowledge, This is the standard one.

TNR,

Saurabh...

Former Member
0 Kudos

You mean the standard usage type of internal leafs is to make parent nodes selectable?

Thanks,

Ingo

Former Member
0 Kudos

Hi,

This is the standard behaviour of MDM that you can only select the leaf nodes.But while syndicating records out from MDM there is an option to send the entire tree instead of only leaves.

Regards,

Jitesh Talreja

Former Member
0 Kudos

Thanks Jitesh.

But I need to know whether the purpose of internal leafs is to make parent nodes selectable in a hierarchy lookup. I can't find any information in the Console Reference Guide about this.

In the example given I want to be able to assign an employee to Organization A.