mapping one record

Venkat

I have many record nodes in the destination schema but i do need only one in
them and the rest should not be generated after the mapping. can any one
pls guide how to do this in the map? (I am not using orchestration, just
plain mapping.)

eg:

source schema Desn schema
-------------------------------------
record1-------------record1
----------------------record2
----------------------record3

i dont need these record2 and record3, note that the elements in the record2
and 3 has some default values.

thanks.
venkat.

Kerrey Zheng

the fields will appear in destination message if they have default values in
mapping file. unless you use another mapping.
--
Kerrey Zheng


"Venkat" wrote:

> I have many record nodes in the destination schema but i do need only one in
> them and the rest should not be generated after the mapping. can any one
> pls guide how to do this in the map? (I am not using orchestration, just
> plain mapping.)
>
> eg:
>
> source schema Desn schema
> -------------------------------------
> record1-------------record1
> ----------------------record2
> ----------------------record3
>
> i dont need these record2 and record3, note that the elements in the record2
> and 3 has some default values.
>
> thanks.
> venkat.
>

Richard Seroter

Yes, so unless you either (a) map an incoming field to those "extra" records,
or (b) set a default value, they won't exist in the final message.
--
Richard Seroter



"Kerrey Zheng" wrote:

> the fields will appear in destination message if they have default values in
> mapping file. unless you use another mapping.
> --
> Kerrey Zheng
>
>
> "Venkat" wrote:
>
> > I have many record nodes in the destination schema but i do need only one in
> > them and the rest should not be generated after the mapping. can any one
> > pls guide how to do this in the map? (I am not using orchestration, just
> > plain mapping.)
> >
> > eg:
> >
> > source schema Desn schema
> > -------------------------------------
> > record1-------------record1
> > ----------------------record2
> > ----------------------record3
> >
> > i dont need these record2 and record3, note that the elements in the record2
> > and 3 has some default values.
> >
> > thanks.
> > venkat.
> >

Sid

> I have many record nodes in the destination schema but i do need only one in
> them and the rest should not be generated after the mapping. can any one
> pls guide how to do this in the map? (I am not using orchestration, just
> plain mapping.)
>
> eg:
>
> source schema Desn schema
> -------------------------------------
> record1-------------record1
> ----------------------record2
> ----------------------record3
>
> i dont need these record2 and record3, note that the elements in the record2
> and 3 has some default values.
>
> thanks.
> venkat.

venkat,

If you cannot supress the destination nodes through schema properties, try this:

source schema Desn schema
-------------------------------------
record1--------------------------record1
----logical & functoid (1=0)----record2
----logical & functoid (1=0)----record3

Since 1 will never equal 0, the false conidition should suppress the destination node.

Sid

BizTalk Utilities - Frustration free BizTalk Adapters

narasareddykunam@gmail.com

In desn schema all element must be mapped.If u any element not map
it's error.

narasareddykunam@gmail.com

On Dec 8, 4:37 am, "Sid"<> wrote:
> > I have many record nodes in the destination schema but i do need only one in
> > them and the rest should not be generated after the mapping. can any one
> > pls guide how to do this in the map? (I am not using orchestration, just
> > plain mapping.)
>
> > eg:
>
> > source schema Desn schema
> > -------------------------------------
> > record1-------------record1
> > ----------------------record2
> > ----------------------record3
>
> > i dont need these record2 and record3, note that the elements in the record2
> > and 3 has some default values.
>
> > thanks.
> > venkat.
>
> venkat,
>
> If you cannot supress the destination nodes through schema properties, try this:
>
> source schema Desn schema
> -------------------------------------
> record1--------------------------record1
> ----logical & functoid (1=0)----record2
> ----logical & functoid (1=0)----record3
>
> Since 1 will never equal 0, the false conidition should suppress the destination node.
>
> Sid
>
> BizTalk Utilities - Frustration free BizTalk Adaptershttp://www.topxml.com/biztalkutilities

take one content functiod assign null value and assign to all elements
in desn schema except you required element. IN source schema you take
only requried element. There is no need to mapp all source elements.