|
Home > Archive > BizTalk Server Tools > April 2005 > Combining Multiple Source Nodes into one destination node
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Combining Multiple Source Nodes into one destination node
|
|
|
| Hello,
I have a source schema that looks similar to the following:
<RootNode>
<Balance>
<Account />
<Amount />
<Date />
</Balance>
<Position>
<Account />
<Amount />
<Date />
<CUSIP />
<Symbol />
</Position>
</RootNode>
The Balance and Position nodes are fairly similar, and I want to map them to
the same destination node:
<Position>
<Account />
<Amount />
<Date />
<CUSIP />
<Symbol />
</Position>
With Positions matching up exactly and Balances only filling out the nodes
that Balances have.
I tried to do this in Biztalk Mapper by just mapping the fields, but I got
some funky results where I had the number of expected Balances, but all the
nodes where just repeats of the Positions.
Can someone show me how to do this properly?
Thanks,
Ely
| |
|
| I did find out how to do this and wanted to share it.
I had to use a looping functoid. I hooked both the main Balance node and
the main Position node from the source up to the same looping functoid, and
then mapped all the child values over as normal. This way the mapper knew
that it needed to loop through both the Balance nodes and the Position
nodes.
"Ely" <elyl@ianinc.com> wrote in message
news:ukHONhaSFHA.3720@TK2MSFTNGP10.phx.gbl...
> Hello,
>
> I have a source schema that looks similar to the following:
>
> <RootNode>
> <Balance>
> <Account />
> <Amount />
> <Date />
> </Balance>
> <Position>
> <Account />
> <Amount />
> <Date />
> <CUSIP />
> <Symbol />
> </Position>
> </RootNode>
>
> The Balance and Position nodes are fairly similar, and I want to map them
> to the same destination node:
>
> <Position>
> <Account />
> <Amount />
> <Date />
> <CUSIP />
> <Symbol />
> </Position>
>
> With Positions matching up exactly and Balances only filling out the nodes
> that Balances have.
>
> I tried to do this in Biztalk Mapper by just mapping the fields, but I got
> some funky results where I had the number of expected Balances, but all
> the nodes where just repeats of the Positions.
>
> Can someone show me how to do this properly?
>
> Thanks,
> Ely
>
>
| |
|
| I did find out how to do this and wanted to share it.
I had to use a looping functoid. I hooked both the main Balance node and
the main Position node from the source up to the same looping functoid, and
then mapped all the child values over as normal. This way the mapper knew
that it needed to loop through both the Balance nodes and the Position
nodes.
"Ely" <elyl@ianinc.com> wrote in message
news:ukHONhaSFHA.3720@TK2MSFTNGP10.phx.gbl...
> Hello,
>
> I have a source schema that looks similar to the following:
>
> <RootNode>
> <Balance>
> <Account />
> <Amount />
> <Date />
> </Balance>
> <Position>
> <Account />
> <Amount />
> <Date />
> <CUSIP />
> <Symbol />
> </Position>
> </RootNode>
>
> The Balance and Position nodes are fairly similar, and I want to map them
> to the same destination node:
>
> <Position>
> <Account />
> <Amount />
> <Date />
> <CUSIP />
> <Symbol />
> </Position>
>
> With Positions matching up exactly and Balances only filling out the nodes
> that Balances have.
>
> I tried to do this in Biztalk Mapper by just mapping the fields, but I got
> some funky results where I had the number of expected Balances, but all
> the nodes where just repeats of the Positions.
>
> Can someone show me how to do this properly?
>
> Thanks,
> Ely
>
>
|
|
|
|
|