Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

BizTalk Mapper Help

151 views
Skip to first unread message

murph...@sbcglobal.net

unread,
May 31, 2007, 12:28:27 PM5/31/07
to
I have an XML with an element of <freightTerms>. If the value of this
element is "PREPAID" then I want to create a NEW <Address> node like
the following.

<Address>
<addressName>BillTo</addressName>
<addressShortName>BT</addressShortName>
</Address>

I am already mapping 2 nodes to the destination XML irregardless of
freightTerms. So I will have a ShipTo and a ShipFrom and only have a
BillTo if the freightTerms in PREPAID.

I can't find a way to do it with functoids. I have no idea how to do
XSL. Any help?

Saravana Kumar

unread,
May 31, 2007, 1:26:03 PM5/31/07
to
You need to use Logical Equal and Value mapping functoid to achive your
output. If you have difficulties, post back to the newsgroup.

--
Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]

murph...@sbcglobal.net

unread,
May 31, 2007, 2:18:25 PM5/31/07
to
I've obvousily tried to use the value mapping funtoid. This is what I
get.

warning btm1005: The destination node "addressRoleName" has 2 data
input(s). The maximum number of possible data inputs to this node is
1.

And

<Address>
<addressRoleName>ShipTo</addressRoleName>
<addressRoleName>BillFreightTo</addressRoleName>
<addressShortName>0000006962</addressShortName>
<addressShortName>POWERTRACK</addressShortName>
</Address>
<Address>
<addressRoleName>ShipFrom</addressRoleName>
<addressRoleName>BillFreightTo</addressRoleName>
<addressShortName>105</addressShortName>
<addressShortName>POWERTRACK</addressShortName>
</Adreess>

While yes, I do get the elements... they are not in a new node. As I
mentioned in my orginal post, I am already mapping values from the
source XML to the destination XML. My understanding is that only one
link can exist in to the destination elements.

I really, really need to get this done this week. The entire team is
waiting on me to finish.

_Abhi_

unread,
May 31, 2007, 2:58:01 PM5/31/07
to
Another way to go about it is to have to Repeating address nodes in the
destination XML and supress the second one when the condition is not met
using a combination of looping and logical functoids. This uses a behaviour
of looping functoid when connected with a logical functoid can supress the
node creation if you want .

Could you post your original XML and then the response XML the way you want
,It is a little confusing the way you have written it.

--
Abhialsh M S

Leonid Ganeline

unread,
May 31, 2007, 3:51:53 PM5/31/07
to
Realy I don't understand what you want.
Could you, please give us the source and target (desirable) xml?

--
Regards,

Leonid Ganeline

Microsoft Certified Technology Specialist: BizTalk Server 2006
http://geekswithblogs.net/leonidganeline/


<murph...@sbcglobal.net> wrote in message
news:1180635505.0...@p77g2000hsh.googlegroups.com...

murph...@sbcglobal.net

unread,
May 31, 2007, 4:35:31 PM5/31/07
to
What I have is this.

<recordset>
<Shipment>
<freightBillingTerms>PREPAID</freightBillingTerms>
<Address>
<addressRoleName>ShipTo</addressRoleName>
<companyName>NAME</companyName>
<addressShortName>NUMBER</addressShortName>
<address1>ADDY</address1>
<address2 />
<address3 />
<city>CITY</city>
<stateProv>ST</stateProv>
<country>US</country>
<postalCode>12345</postalCode>


</Address>
<Address>
<addressRoleName>ShipFrom</addressRoleName>

<companyName>ME</companyName>
<addressShortName>NUM</addressShortName>
<participantKey>KEY</participantKey>
<locationName>LOCALE</locationName>
<address1 />
<address2 />
<address3>Street</address3>
<city>City</city>
<stateProv>ST</stateProv>
<country>US</country>
<postalCode>12345</postalCode>
</Address>
</Shipment>
</recordset>

What I want is this.

<recordset>
<Shipment>
<freightBillingTerms>PREPAID</freightBillingTerms>
<Address>
<addressRoleName>ShipTo</addressRoleName>
<companyName>NAME</companyName>
<addressShortName>NUMBER</addressShortName>
<address1>ADDY</address1>
<address2 />
<address3 />
<city>CITY</city>
<stateProv>ST</stateProv>
<country>US</country>
<postalCode>12345</postalCode>


</Address>
<Address>
<addressRoleName>ShipFrom</addressRoleName>

<companyName>ME</companyName>
<addressShortName>NUM</addressShortName>
<participantKey>KEY</participantKey>
<locationName>LOCALE</locationName>
<address1 />
<address2 />
<address3>Street</address3>
<city>City</city>
<stateProv>ST</stateProv>
<country>US</country>
<postalCode>12345</postalCode>
</Address>
<Address>
<addressRoleName>BillTo</addressRoleName>
<addressShortName>NUM</addressShortName>
</Address>
</Shipment>
</recordset>

Notice the addition of the new address node after the ShipFrom Address
node.

Jan Eliasen

unread,
May 31, 2007, 5:43:38 PM5/31/07
to
On 31 May 2007 13:35:31 -0700, murph...@sbcglobal.net wrote:

>What I have is this.

I never found a better solution than:
http://blog.eliasen.dk/Default.aspx#a44fab7d1-edde-4d75-b477-6e1dc676c34a

I'd be happy to hear about it, if you find a better way, though!

--
eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: j...@eliasen.dk

Leonid Ganeline

unread,
Jun 1, 2007, 12:07:01 PM6/1/07
to
I'd propose simple Script functoid: Inline XSLT
- No inputs,
- Output to the <Address> node

<xsl:if test="ns0:Shipment/freightBillingTerms/text()='PREPAID'">
<Address>
<addressRoleName>
<xsl:value-of select="xPath..." />
</addressRoleName>
<addressShortName>
<xsl:value-of select="xPath..." />
</addressShortName>
</Address>
</xsl:if>


Regards,

Leonid Ganeline

Microsoft Certified Technology Specialist: BizTalk Server 2006
http://geekswithblogs.net/leonidganeline/

Jan Eliasen

unread,
Jun 3, 2007, 2:35:09 PM6/3/07
to
On Fri, 1 Jun 2007 09:07:01 -0700, Leonid Ganeline
<LeonidG...@discussions.microsoft.com> wrote:

>I'd propose simple Script functoid: Inline XSLT
>- No inputs,
>- Output to the <Address> node
>
><xsl:if test="ns0:Shipment/freightBillingTerms/text()='PREPAID'">
> <Address>
> <addressRoleName>
> <xsl:value-of select="xPath..." />
> </addressRoleName>
> <addressShortName>
> <xsl:value-of select="xPath..." />
> </addressShortName>
> </Address>
></xsl:if>

I tried this solution, but I could never get it to work, since he also
needs to map existing Address elements from the source to Address
elements in the destination. The combination of letting the mapper
create some of the Address elements and having XSLT create the last
one... I never got it working. Do you have a working example you can
show me?

Leonid Ganeline

unread,
Jun 4, 2007, 6:27:22 PM6/4/07
to
Yeah, sure,
I use this approach all the time:

<Weight>
<xsl:for-each select="ns0:MEA_2">
<xsl:if test="ns0:MEA01/text()='AAE'">
<xsl:if test="ns0:C502_2/ns0:C50201/text()='G'">
<Value>
<xsl:value-of select="ns0:C174_2/ns0:C17402/text()" />
</Value>
<Unit>
<xsl:value-of select="ns0:C174_2/ns0:C17401/text()" />
</Unit>
</xsl:if>
</xsl:if>
</xsl:for-each>
</Weight>

The most frequent mistake I do usually is
if I have
<ns0:C502_2>
<ns0:C50201>..
I must use:
ns0:C502_2/ns0:C50201
if I have
<ns0:C502_2>
<C50201>..
I must use:
ns0:C502_2/C50201

The prefixes in my Xml file must be exactly the same as in XPathes.

Next mistake is: the target node is crated on the wrong level. I check Xslt
to make sure I make the right link from Inline Xslt to the target schema in
a map.

--
Regards,

Leonid Ganeline

Microsoft Certified Technology Specialist: BizTalk Server 2006
http://geekswithblogs.net/leonidganeline/


"Jan Eliasen" <eli...@nospam.nospam> wrote in message
news:vc2663ht4ii70i7q8...@4ax.com...

Jan Eliasen

unread,
Jun 5, 2007, 5:48:18 PM6/5/07
to
On Mon, 4 Jun 2007 15:27:22 -0700, "Leonid Ganeline"
<leo_g...@hotmail.com> wrote:

>Yeah, sure,
>I use this approach all the time:

I don't think your example covers the issue. The issue is that he must
have two Address nodes from the source schema mapped to the
destination schema, and ALSO, create a third Address node in the
output depending on some value later on. You are only creating the one
node, depending on the value - you are not also copying the existing
nodes.

murph...@sbcglobal.net

unread,
Jun 7, 2007, 11:53:17 AM6/7/07
to
Jan is right. I need the two original and a third new node.

Leonid Ganeline

unread,
Jun 7, 2007, 4:36:01 PM6/7/07
to
Yes, of course, these two original nodes should be created in map. I didn't
mention them, this obvious.
The Inline Xslt should be after mapping those two nodes.

murph...@sbcglobal.net

unread,
Jun 8, 2007, 4:07:10 PM6/8/07
to
If I output to the Address node I get warning "Element has two data
inputs when only 1 is allowed"

And, I get this as the output.

<addressRoleName>ShipTo</addressRoleName>
<companyName>name</companyName>
<addressShortName>0000006962</addressShortName>
<address1>addy/address1>
<address2 />
<address3>addy</address3>
<city>city</city>


<stateProv>ST</stateProv>
<country>US</country>

<postalCode>66601</postalCode>
<Shipment>
<Address>
<addressRoleName>BillFreightTo</addressRoleName>
<addressShortName>BT</addressShortName>
</Address>
</Shipment>
<addressRoleName>ShipFrom</addressRoleName>
<companyName>name</companyName>
<addressShortName>short</addressShortName>
<participantKey>key</participantKey>
<locationName>locale</locationName>
<address1 />
<address2 />
<address3>addy</address3>
<city>city</city>
<stateProv>st</stateProv>
<country>US</country>
<postalCode>66602</postalCode>
<Shipment>
<Address>
<addressRoleName>BillFreightTo</addressRoleName>
<addressShortName>BT</addressShortName>
</Address>
</Shipment>

The shipment XML for the ShipTo and ShipFrom is missing and the XSLT
is repeated twice.

Leonid Ganeline

unread,
Jun 8, 2007, 4:59:00 PM6/8/07
to
To resolve this issue:
Look at the Xslt generated by mapper (creates by Validate map command).
Extrude from it the part about Address, then add this part to the custom
Xslt inline script under the right If branch. It depends of what you want.
Then change the cardinality (max occurs) of the Address node to 4 (or..what
you want).

But!
I'd propose you review the target schema.
Why?
Because you have now two nodes (Addresses with the same names but different
purpose).
If you give them different names (first Addresses are not the same as
seconds) that resolve previous issue and moreover resolve more serious a
name-purpose conflict.

murph...@sbcglobal.net

unread,
Jun 8, 2007, 5:10:30 PM6/8/07
to
I want to thank everyone for their input and discussion.

This was my first post on Google groups and I've been really please
with the response.

For the sake of history. This is what I did to solve my issue.

<xsl:for-each select="/*[local-name()='recordset' and namespace-
uri()='']/*[local-name()='Shipment' and namespace-uri()='']/*[local-
name()='Address' and namespace-uri()='']">
<xsl:element name="Address">
<xsl:element name="addressRoleName"><xsl:value-of
select="addressRoleName" /></xsl:element>
<xsl:element name="defaultContactName"><xsl:value-of
select="defaultContactName" /></xsl:element>
<xsl:element name="companyName"><xsl:value-of select="companyName" /
></xsl:element>
<xsl:element name="addressShortName"><xsl:value-of
select="addressShortName" /></xsl:element>
<xsl:element name="participantKey"><xsl:value-of
select="participantKey" /></xsl:element>
<xsl:element name="locationName"><xsl:value-of
select="locationName" /></xsl:element>
<xsl:element name="address1"><xsl:value-of select="address1" /></
xsl:element>
<xsl:element name="address2"><xsl:value-of select="address2" /></
xsl:element>
<xsl:element name="address3"><xsl:value-of select="address3" /></
xsl:element>
<xsl:element name="city"><xsl:value-of select="city" /></
xsl:element>
<xsl:element name="stateProv"><xsl:value-of select="stateProv" /></
xsl:element>
<xsl:element name="country"><xsl:value-of select="country" /></
xsl:element>
<xsl:element name="postalCode"><xsl:value-of select="postalCode" /></
xsl:element>
<xsl:element name="afterHoursPhone"><xsl:value-of
select="afterHoursPhone" /></xsl:element>
<xsl:element name="workPhone"><xsl:value-of select="workPhone" /></
xsl:element>
<xsl:element name="faxCountryCode"><xsl:value-of
select="faxCountryCode" /></xsl:element>
<xsl:element name="faxAreaCode"><xsl:value-of select="faxAreaCode" /
></xsl:element>
<xsl:element name="faxNumber"><xsl:value-of select="faxNumber" /></
xsl:element>
<xsl:element name="enableEmailNotification"><xsl:value-of
select="enableEmailNotification" /></xsl:element>
<xsl:element name="enableFaxNotification"><xsl:value-of
select="enableFaxNotification" /></xsl:element>
<xsl:element name="email"><xsl:value-of select="email" /></
xsl:element>
<xsl:element name="standardPointLocationCode"><xsl:value-of
select="standardPointLocationCode" /></xsl:element>
<xsl:element name="standardCarrierAlphaCode"><xsl:value-of
select="standardCarrierAlphaCode" /></xsl:element>
<xsl:element name="timezoneName"><xsl:value-of
select="timezoneName" /></xsl:element>
</xsl:element>
</xsl:for-each>

<xsl:variable name="freightTermsValue" select="/*[local-
name()='recordset' and namespace-uri()='']/*[local-name()='Shipment'
and namespace-uri()='']/*[local-name()='freightBillingTerms' and
namespace-uri()='']/text()" />
<xsl:choose>
<xsl:when test="$freightTermsValue = 'PREPAID'">
<xsl:element name="Address">
<xsl:element name="addressRoleName">BillFreightTo</xsl:element>
<xsl:element name="addressShortName">BT</xsl:element>
</xsl:element>
</xsl:when>
<xsl:otherwise>
</xsl:otherwise>
</xsl:choose>

Jan Eliasen

unread,
Jun 8, 2007, 5:41:54 PM6/8/07
to
On Thu, 7 Jun 2007 13:36:01 -0700, Leonid Ganeline
<LeonidG...@discussions.microsoft.com> wrote:

>Yes, of course, these two original nodes should be created in map. I didn't
>mention them, this obvious.
>The Inline Xslt should be after mapping those two nodes.

Have you tested it? I have never been able to get this working. I
always resolve to letting the xslt functoid copy the existing nodes
and then create the new node. As I have described here:
http://blog.eliasen.dk/PermaLink,guid,44fab7d1-edde-4d75-b477-6e1dc676c34a.aspx

Jan Eliasen

unread,
Jun 8, 2007, 5:43:29 PM6/8/07
to
On Fri, 8 Jun 2007 13:59:00 -0700, Leonid Ganeline
<LeonidG...@discussions.microsoft.com> wrote:

>To resolve this issue:
>Look at the Xslt generated by mapper (creates by Validate map command).
>Extrude from it the part about Address, then add this part to the custom
>Xslt inline script under the right If branch. It depends of what you want.
>Then change the cardinality (max occurs) of the Address node to 4 (or..what
>you want).

So.. you need the full functionality inside a scripting functoid and
can not maps the existing nodes using the mapper and create a new node
using the scripting functoid?

Leonid Ganeline

unread,
Jun 8, 2007, 6:18:01 PM6/8/07
to
Hey! this is MSDN group! :))
Please, click "This post is answer..." button :)

Thanks to be so patient!

Leonid Ganeline

unread,
Jun 8, 2007, 6:34:01 PM6/8/07
to
Jan,
not sure I understand you "to letting the xslt functoid copy the existing
nodes
and then create the new node." The article didn't help me.
Could you, please, give more information?

My experience: the Xslt inline functoid can create different results depends
of how the BizTalk mapper generated the "upper-level" record.
To get desirable result I always look at the xslt generated by mapper, to
make sure my xslt take and put right XPath-es and to right place in target
schema.

Jan Eliasen

unread,
Jun 9, 2007, 3:55:38 AM6/9/07
to
On Fri, 8 Jun 2007 15:34:01 -0700, Leonid Ganeline
<LeonidG...@discussions.microsoft.com> wrote:

>not sure I understand you "to letting the xslt functoid copy the existing
>nodes
>and then create the new node." The article didn't help me.

In the post I answered, you wrote this:
-- BEGIN


Yes, of course, these two original nodes should be created in map. I
didn't
mention them, this obvious.
The Inline Xslt should be after mapping those two nodes.

-- END
I am saying that I have never been able to do this. I must always have
a xslt functoid create ALL the destination nodes - both the ones that
should be copied form the source and the new node that must be
created.

But your post seems to indicate that I should be able to do it witout
having the XSLT functoid copy the existing nodes and let the mapper do
this. I was just wondering if you have an example of how you do that?

Leonid Ganeline

unread,
Jun 9, 2007, 5:52:00 PM6/9/07
to
Jan you are absolutely right about "not mixing graphic mapping with Xslt
inline". We also (with Murphy) discussed this in the main branch of this
topic.
I just misundestand your reply.

Thanks for interesting discussion!

Jan Eliasen

unread,
Jun 10, 2007, 5:15:27 PM6/10/07
to
On Sat, 9 Jun 2007 14:52:00 -0700, Leonid Ganeline
<LeonidG...@discussions.microsoft.com> wrote:

>Jan you are absolutely right about "not mixing graphic mapping with Xslt
>inline". We also (with Murphy) discussed this in the main branch of this
>topic.
>I just misundestand your reply.
>
>Thanks for interesting discussion!

Same to you... and glad we agree - next time, lets not talk past
eachother, but talk the same language from the beginning .-)

Leonid Ganeline

unread,
Jun 11, 2007, 12:05:01 PM6/11/07
to
:)

bhupalrathod

unread,
Nov 5, 2009, 8:34:52 AM11/5/09
to
Hi,
I have similar kind of issue what you faced and resolved.I am new to BizTalk so i am unable to catch your thoughts.
Here is my scenario:
I have Header and Itme data from source and i should create from this two information,4 lines of data like 1st Header data(Non Repeatable), 2nd Header+Line item data if VAT field value available,3rd Header+Line item data with Calculated VAT,4th Header and Item actual data.
I will send you my source and target files if you have time to look at it.
Please help this is critical and pending from my side.

Thanks,
Bhupal.

murphyada wrote:

I want to thank everyone for their input and discussion.

08-Jun-07

I want to thank everyone for their input and discussion.

This was my first post on Google groups and I've been really please
with the response.

For the sake of history. This is what I did to solve my issue.

<xsl:for-each select="/*[local-name()='recordset' and namespace-
uri()='']/*[local-name()='Shipment' and namespace-uri()='']/*[local-
name()='Address' and namespace-uri()='']">
<xsl:element name="Address">
<xsl:element name="addressRoleName"><xsl:value-of
select="addressRoleName" /></xsl:element>
<xsl:element name="defaultContactName"><xsl:value-of
select="defaultContactName" /></xsl:element>
<xsl:element name="companyName"><xsl:value-of select="companyName" /

Previous Posts In This Thread:

On Thursday, May 31, 2007 12:28 PM
murphyada wrote:

BizTalk Mapper Help


I have an XML with an element of <freightTerms>. If the value of this
element is "PREPAID" then I want to create a NEW <Address> node like
the following.

<Address>
<addressName>BillTo</addressName>
<addressShortName>BT</addressShortName>
</Address>

I am already mapping 2 nodes to the destination XML irregardless of
freightTerms. So I will have a ShipTo and a ShipFrom and only have a
BillTo if the freightTerms in PREPAID.

I can't find a way to do it with functoids. I have no idea how to do
XSL. Any help?

On Thursday, May 31, 2007 1:26 PM
saravanam wrote:

You need to use Logical Equal and Value mapping functoid to achive your output.
You need to use Logical Equal and Value mapping functoid to achive your
output. If you have difficulties, post back to the newsgroup.

--
Regards,
Saravana Kumar
http://www.biztalk247.com/v1/
http://www.digitaldeposit.net/blog
[Please mark the response as "Answer" if it solves your problem.]


"murph...@sbcglobal.net" wrote:

On Thursday, May 31, 2007 2:18 PM
murphyada wrote:

I've obvousily tried to use the value mapping funtoid. This is what Iget.
I've obvousily tried to use the value mapping funtoid. This is what I
get.

warning btm1005: The destination node "addressRoleName" has 2 data
input(s). The maximum number of possible data inputs to this node is
1.

And

<Address>
<addressRoleName>ShipTo</addressRoleName>
<addressRoleName>BillFreightTo</addressRoleName>
<addressShortName>0000006962</addressShortName>
<addressShortName>POWERTRACK</addressShortName>

</Address>
<Address>
<addressRoleName>ShipFrom</addressRoleName>

<addressRoleName>BillFreightTo</addressRoleName>
<addressShortName>105</addressShortName>
<addressShortName>POWERTRACK</addressShortName>
</Adreess>

While yes, I do get the elements... they are not in a new node. As I
mentioned in my orginal post, I am already mapping values from the
source XML to the destination XML. My understanding is that only one
link can exist in to the destination elements.

I really, really need to get this done this week. The entire team is
waiting on me to finish.

On Thursday, May 31, 2007 2:58 PM
Abh wrote:

Another way to go about it is to have to Repeating address nodes in the
Another way to go about it is to have to Repeating address nodes in the
destination XML and supress the second one when the condition is not met
using a combination of looping and logical functoids. This uses a behaviour
of looping functoid when connected with a logical functoid can supress the
node creation if you want .

Could you post your original XML and then the response XML the way you want
,It is a little confusing the way you have written it.

--
Abhialsh M S

"murph...@sbcglobal.net" wrote:

On Thursday, May 31, 2007 3:51 PM
Leonid Ganeline wrote:

Realy I don't understand what you want.
Realy I don't understand what you want.
Could you, please give us the source and target (desirable) xml?

--
Regards,

Leonid Ganeline

Microsoft Certified Technology Specialist: BizTalk Server 2006
http://geekswithblogs.net/leonidganeline/

<murph...@sbcglobal.net> wrote in message
news:1180635505.0...@p77g2000hsh.googlegroups.com...

On Thursday, May 31, 2007 4:35 PM
murphyada wrote:

What I have is this.
What I have is this.

<recordset>
<Shipment>
<freightBillingTerms>PREPAID</freightBillingTerms>
<Address>
<addressRoleName>ShipTo</addressRoleName>
<companyName>NAME</companyName>
<addressShortName>NUMBER</addressShortName>
<address1>ADDY</address1>
<address2 />
<address3 />

<city>CITY</city>


<stateProv>ST</stateProv>
<country>US</country>

<postalCode>12345</postalCode>
</Address>
<Address>
<addressRoleName>ShipFrom</addressRoleName>
<companyName>ME</companyName>
<addressShortName>NUM</addressShortName>
<participantKey>KEY</participantKey>

<locationName>LOCALE</locationName>
<address1 />
<address2 />
<address3>Street</address3>
<city>City</city>


<stateProv>ST</stateProv>
<country>US</country>

<postalCode>12345</postalCode>
</Address>
</Shipment>
</recordset>

What I want is this.

<recordset>
<Shipment>
<freightBillingTerms>PREPAID</freightBillingTerms>
<Address>
<addressRoleName>ShipTo</addressRoleName>
<companyName>NAME</companyName>
<addressShortName>NUMBER</addressShortName>
<address1>ADDY</address1>
<address2 />
<address3 />

<city>CITY</city>


<stateProv>ST</stateProv>
<country>US</country>

<postalCode>12345</postalCode>
</Address>
<Address>
<addressRoleName>ShipFrom</addressRoleName>
<companyName>ME</companyName>
<addressShortName>NUM</addressShortName>
<participantKey>KEY</participantKey>

<locationName>LOCALE</locationName>
<address1 />
<address2 />
<address3>Street</address3>
<city>City</city>


<stateProv>ST</stateProv>
<country>US</country>

<postalCode>12345</postalCode>
</Address>
<Address>
<addressRoleName>BillTo</addressRoleName>
<addressShortName>NUM</addressShortName>
</Address>
</Shipment>
</recordset>

Notice the addition of the new address node after the ShipFrom Address
node.

On Thursday, May 31, 2007 5:43 PM
Jan Eliasen wrote:

Re: BizTalk Mapper Help


On 31 May 2007 13:35:31 -0700, murph...@sbcglobal.net wrote:

I never found a better solution than:
http://blog.eliasen.dk/Default.aspx#a44fab7d1-edde-4d75-b477-6e1dc676c34a

I'd be happy to hear about it, if you find a better way, though!

--

eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: j...@eliasen.dk

On Friday, June 01, 2007 12:07 PM
LeonidGanelin wrote:

Re: BizTalk Mapper Help


I'd propose simple Script functoid: Inline XSLT
- No inputs,
- Output to the <Address> node

<xsl:if test="ns0:Shipment/freightBillingTerms/text()='PREPAID'">
<Address>
<addressRoleName>
<xsl:value-of select="xPath..." />
</addressRoleName>
<addressShortName>
<xsl:value-of select="xPath..." />
</addressShortName>
</Address>
</xsl:if>


Regards,

Leonid Ganeline

Microsoft Certified Technology Specialist: BizTalk Server 2006
http://geekswithblogs.net/leonidganeline/

"murph...@sbcglobal.net" wrote:

On Sunday, June 03, 2007 2:35 PM
Jan Eliasen wrote:

Re: BizTalk Mapper Help


On Fri, 1 Jun 2007 09:07:01 -0700, Leonid Ganeline
<LeonidG...@discussions.microsoft.com> wrote:

I tried this solution, but I could never get it to work, since he also
needs to map existing Address elements from the source to Address
elements in the destination. The combination of letting the mapper
create some of the Address elements and having XSLT create the last
one... I never got it working. Do you have a working example you can
show me?

--

eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: j...@eliasen.dk

On Monday, June 04, 2007 6:27 PM
Leonid Ganeline wrote:

Re: BizTalk Mapper Help


Yeah, sure,
I use this approach all the time:

<Weight>

--
Regards,

Leonid Ganeline

On Tuesday, June 05, 2007 5:48 PM
Jan Eliasen wrote:

Re: BizTalk Mapper Help


On Mon, 4 Jun 2007 15:27:22 -0700, "Leonid Ganeline"
<leo_g...@hotmail.com> wrote:

I don't think your example covers the issue. The issue is that he must
have two Address nodes from the source schema mapped to the
destination schema, and ALSO, create a third Address node in the
output depending on some value later on. You are only creating the one
node, depending on the value - you are not also copying the existing
nodes.

--

eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: j...@eliasen.dk

On Thursday, June 07, 2007 11:53 AM
murphyada wrote:

Jan is right. I need the two original and a third new node.
Jan is right. I need the two original and a third new node.

On Thursday, June 07, 2007 4:36 PM
LeonidGanelin wrote:

Yes, of course, these two original nodes should be created in map.

Yes, of course, these two original nodes should be created in map. I did not


mention them, this obvious.
The Inline Xslt should be after mapping those two nodes.

On Friday, June 08, 2007 4:07 PM
murphyada wrote:

On Friday, June 08, 2007 4:59 PM
LeonidGanelin wrote:

Re: BizTalk Mapper Help


To resolve this issue:
Look at the Xslt generated by mapper (creates by Validate map command).
Extrude from it the part about Address, then add this part to the custom
Xslt inline script under the right If branch. It depends of what you want.
Then change the cardinality (max occurs) of the Address node to 4 (or..what
you want).

But!


I'd propose you review the target schema.
Why?
Because you have now two nodes (Addresses with the same names but different
purpose).
If you give them different names (first Addresses are not the same as
seconds) that resolve previous issue and moreover resolve more serious a
name-purpose conflict.

"murph...@sbcglobal.net" wrote:

On Friday, June 08, 2007 5:10 PM
murphyada wrote:

I want to thank everyone for their input and discussion.
I want to thank everyone for their input and discussion.

This was my first post on Google groups and I've been really please
with the response.

For the sake of history. This is what I did to solve my issue.

<xsl:for-each select="/*[local-name()='recordset' and namespace-
uri()='']/*[local-name()='Shipment' and namespace-uri()='']/*[local-
name()='Address' and namespace-uri()='']">
<xsl:element name="Address">
<xsl:element name="addressRoleName"><xsl:value-of
select="addressRoleName" /></xsl:element>
<xsl:element name="defaultContactName"><xsl:value-of
select="defaultContactName" /></xsl:element>
<xsl:element name="companyName"><xsl:value-of select="companyName" /

On Friday, June 08, 2007 6:18 PM
LeonidGanelin wrote:

Hey! this is MSDN group!
Hey! this is MSDN group! :))
Please, click "This post is answer..." button :)

Thanks to be so patient!

On Friday, June 08, 2007 6:34 PM
LeonidGanelin wrote:

Jan,not sure I understand you "to letting the xslt functoid copy the existing
Jan,


not sure I understand you "to letting the xslt functoid copy the existing
nodes
and then create the new node." The article didn't help me.

Could you, please, give more information?

My experience: the Xslt inline functoid can create different results depends
of how the BizTalk mapper generated the "upper-level" record.
To get desirable result I always look at the xslt generated by mapper, to
make sure my xslt take and put right XPath-es and to right place in target
schema.

"Jan Eliasen" wrote:

On Saturday, June 09, 2007 5:52 PM
LeonidGanelin wrote:

Jan you are absolutely right about "not mixing graphic mapping with Xslt
Jan you are absolutely right about "not mixing graphic mapping with Xslt
inline". We also (with Murphy) discussed this in the main branch of this
topic.
I just misundestand your reply.

Thanks for interesting discussion!

"Jan Eliasen" wrote:

On Monday, June 11, 2007 12:05 PM
LeonidGanelin wrote:

Re: BizTalk Mapper Help
"Jan Eliasen" wrote:

EggHeadCafe - Software Developer Portal of Choice
ASP.NET Modal Dialog Postback and return values
http://www.eggheadcafe.com/tutorials/aspnet/f6a080a9-3394-4299-855c-f0128810f738/aspnet-modal-dialog-post.aspx

0 new messages