cancel
Showing results for 
Search instead for 
Did you mean: 

context and context change?

Former Member
0 Kudos

What is context and context change?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Context : Context of an element is nothing but just the level, where

the XML tag appears in the given XML

document. Level of any element is set to the immediate parent node by

default.

Context Change : Context change is just changing the level of XML

tag(element level in XSD) in the XML document.

This means when we map one source field to one target field then that

both field segments should be at same

level.

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Context means it is the level in XML like parent node. Root node

Ex:

<root>

<header name=u201CA">

<item>A.one</item>

<item>A.two</item>

<item>A.three</item>

</header>

<header name="B">

<item>B.one</item>

<item>B.two</item>

</header>

</root>

Here Context item, header and root are the different contexts for A.one. If you used display queue in your mapping it will separte all contexts by a dark line.

If you want to combile both A and B you have to change the context to removing context.

If there is duplication of A.one,A.two,A.three you have to change context to header(by default it is item level).This you can achieve in message mapping.

Suppose you have one element in source and you have to map to multiple elements in target. then split the context and send to target.

Reward points if needful.

Thanks,

RamuV

Former Member
0 Kudos

Hi,

Context are used in graphical mapping in XI. Contexts are used to change the hierarchy of data while developing the Graphical mapping.

You can see context as a small black line in the Graphical mapping editor. There are different inbuilt functions in XI to change the context hierarchy like removecontext etc.

Kulwinder

Award points if helpful

Former Member
0 Kudos

check them

/people/sravya.talanki2/blog/2005/08/16/message-mapping-simplified--part-i

/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii