Problem of building a Mapping in graphic mode

.
Hello,

I would like to export a BOD of type Sync.SalesOrder in a file.

To do this, I followed all the advice and recommendations I read in this forum.

I more or less managed to put all the elements in place and finally managed to produce an on-Premise CSV file.
But, so mechanically, I have some initial successes.
Nevertheless, the content of this file does not match my expectations.

By analyzing my problem step by step, I think that the first cause comes from the mapping phase.
Indeed, I created a custom BOD to simplify the standard BOD and to retain only the few desired fields for my CSV export.
Then I created a mapping between the standard BOD and the Custom BOD.
And when I test it, I see that, for example, if I have a sales order with 4 rows as input, I come out after the mapping with a BOD with only one row accumulating the field values of these 4 rows.

Here are a few screenshots to make it clearer. Where did I go wrong to produce this result? Because even if I created a file template to be able to write in a CSV file, this step only transports the error generated upstream.

<?xml version="1.0" encoding="UTF-8"?>
<!--
Mapping: DMSalesOrder4
Description:
Version: 1
Created by:
Created on:
Last updated by:
Last updated on:
Input: Sync.SalesOrder
Output: Sync.DMSalesOrder4
Product Version: Infor ION 2021-05
XSLT Code Generator: V2

Copyright © 2021 Infor. All rights reserved.
The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or its affiliates and subsidiaries.
All rights reserved. All other trademarks listed herein are the property of their respective owners.
www.infor.com
-->
<xsl:stylesheet version="2.0" xmlns="">schema.infor.com/.../2" xmlns:expath-zip="">http://expath.org/ns/zip" xmlns:fn="">www.w3.org/.../xpath-functions" xmlns:dns="">schema.infor.com/.../2" xmlns:saxon="">http://saxon.sf.net/" xmlns:udf1="">http://infor.com/custom" xmlns:expath-file="">http://expath.org/ns/file" xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:xsl="">www.w3.org/.../Transform" xmlns:exslt-random="">http://exslt.org/random" xmlns:exslt-common="">http://exslt.org/common" xmlns:exslt-math="">http://exslt.org/math" xmlns:xs="">www.w3.org/.../XMLSchema" xmlns:math="">www.w3.org/.../math" xmlns:map="">www.w3.org/.../map" exclude-result-prefixes="xs xsl fn expath-file expath-zip exslt-common exslt-math exslt-random map math saxon xsi ">
<xsl:output method="xml" encoding="UTF-8" indent="no" byte-order-mark="no"/>
<xsl:strip-space elements="*"/>
<xsl:function name="udf1:get-first-value">
<xsl:param name="input-list"/>
<xsl:value-of select="$input-list[1]"/>
</xsl:function>
<xsl:template match="/">
<xsl:element name="SyncDMSalesOrder4">
<xsl:namespace name="xs" select="'">www.w3.org/.../>
<xsl:if test="/*:SyncSalesOrder/@languageCode">
<xsl:attribute name="languageCode">
<xsl:value-of select="/*:SyncSalesOrder/@languageCode"/>
</xsl:attribute>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/@releaseID">
<xsl:attribute name="releaseID">
<xsl:value-of select="/*:SyncSalesOrder/@releaseID"/>
</xsl:attribute>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/@systemEnvironmentCode">
<xsl:attribute name="systemEnvironmentCode">
<xsl:value-of select="/*:SyncSalesOrder/@systemEnvironmentCode"/>
</xsl:attribute>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/@versionID">
<xsl:attribute name="versionID">
<xsl:value-of select="/*:SyncSalesOrder/@versionID"/>
</xsl:attribute>
</xsl:if>
<xsl:copy-of select="/*:SyncSalesOrder/*:ApplicationArea" copy-namespaces="no" />
<xsl:element name="DataArea">
<xsl:copy-of select="/*:SyncSalesOrder/*:DataArea/*:Sync" copy-namespaces="no" />
<xsl:element name="DMSalesOrder4">
<xsl:element name="SampleHeader">
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:DocumentID/*:ID">
<xsl:element name="DocumentID">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:DocumentID/*:ID/text()"/>
</xsl:element>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:DocumentDateTime">
<xsl:element name="DocumentDateTime">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:DocumentDateTime/text()"/>
</xsl:element>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:Status/*:ReasonCode">
<xsl:element name="Status">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:Status/*:ReasonCode/text()"/>
</xsl:element>
</xsl:if>
<xsl:element name="CustomerPartyName">
<xsl:variable name="data000">
<xsl:value-of select="udf1:get-first-value(/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:CustomerParty/*:Name)"/>
</xsl:variable>
<xsl:value-of select="fn:string($data000)"/>
</xsl:element>
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:CustomerParty/*:Location/*:Address/*:CityName">
<xsl:element name="CustomerPartyCityName">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:CustomerParty/*:Location/*:Address/*:CityName/text()"/>
</xsl:element>
</xsl:if>
</xsl:element>
<xsl:element name="SampleLine">
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:LineNumber">
<xsl:element name="LineNumber">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:LineNumber/text()"/>
</xsl:element>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:Item/*:ItemID/*:ID">
<xsl:element name="ItemID">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:Item/*:ItemID/*:ID/text()"/>
</xsl:element>
</xsl:if>
<xsl:element name="ItemDescription">
<xsl:variable name="data000">
<xsl:value-of select="udf1:get-first-value(/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:Description)"/>
</xsl:variable>
<xsl:value-of select="fn:string($data000)"/>
</xsl:element>
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:Quantity">
<xsl:element name="BasisQuantity">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:Quantity/text()"/>
</xsl:element>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:Quantity/@unitCode">
<xsl:element name="UnitCode">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:Quantity/@unitCode"/>
</xsl:element>
</xsl:if>
</xsl:element>
</xsl:element>
</xsl:element>
</xsl:element>
</xsl:template>
</xsl:stylesheet>

Thanks for your advice

Find more posts tagged with

ION Mapper & Scripting

Accepted answers

unknown

Hi,

Whatever you have done in the graphical mode of xslt mapping is correct. But as line details is a repeatative one graphical mode doesn't understand that .

You can move to the xslt editor mode which will freeze the graphical mode and your next logic should be in xslt editor using xslt coding. Do not switch to graphical mode again after using xslt editor for xslt coding

In XSLT editor mode in xslt code you can use for each loop functionality of xslt and then test the results. This should resolve your issue

unknown

Try changing this part:

<xsl:for-each select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:LineNumber/text()">
<xsl:element name="SalesOrderLine">
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:LineNumber">
<xsl:element name="LineNumber">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:LineNumber/text()"/>
</xsl:element>
</xsl:if>
</xsl:element>
</xsl:for-each>

To this:

<xsl:for-each select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine">
<xsl:element name="SalesOrderLine">
<xsl:if test="*:LineNumber">
<xsl:element name="LineNumber">
<xsl:value-of select="*:LineNumber/text()"/>
</xsl:element>
</xsl:if>
</xsl:element>
</xsl:for-each>

When you do xsl:for-each, you are the in a context of that node. But in your example you are referring back to root and then to first Sales order line over and over again. I would skip the "*:" in front of XPath as well..

All comments

Denis MARETTE

Hello,

I'm trying to turn the problem upside down but I don't understand why by using mapping graphing in a basic way, I can't generate a very simplified version of the Standard SalesOrder BOD correctly.

I don't see on which parameter to act so that the mapping operation preserves the 2 level structure header/row?
Here is an example of what I get

In input

<Status>Allocated</Status>

…….

</SalesOrderHeader>

……..

</SalesOrderLine>

……..

</SalesOrderLine>

……..

</SalesOrderLine>

…….

</SalesOrderLine>

</SalesOrder>

In output

<Status>Allocated</Status>

</SalesOrderHeader>

</SalesOrderLine>

</SalesOrder>

Any comment can only be useful. Thanks in advance.

Denis MARETTE

no suggestion about the problem I'm having?

If not, do you have a simple example of a header/detail BOD mapping that you could share with me and load in my environment so that I can find out where my error comes from by comparison

Thanks

unknown

Hi,

Whatever you have done in the graphical mode of xslt mapping is correct. But as line details is a repeatative one graphical mode doesn't understand that .

In XSLT editor mode in xslt code you can use for each loop functionality of xslt and then test the results. This should resolve your issue

Denis MARETTE

Hi @shashank-malali

Thank you for this clarification which finally allows me to understand where my concern comes from
Great!
I am not really a developer. Also, if you have a very simple example of xls with a loop to share, I'm a taker.

Anyway, thanks a lot. I'll be able to move forward because I was stuck on this point;

mpazluna

Hi Denis,

Try mapping the parent element SalesOrderLine to SampleLine. Then map the child elements if needed.

Let me know how it goes.

Best Regards,

Maria

Denis MARETTE

Hi Maria,

Thanks for your answer but I think that's what I had intuitively done.

But it seems that this technique has limits in graphic mode when there are repetitive elements similar to a parent/child or Header/Line relationship.

I let you consult Shashank Malali's answer which invites me to edit in manual mode the automatically generated code to make the necessary changes.

Does-it make sense for you ?

Regards

unknown

Hi Denis,

Here is the sample code. Traverse through the Address in Location (In M3 std BOD), get the values and put them in the tags of custom bod

<xsl:for-each select="*:Location/*:Address">
<xsl:element name ="address">
<xsl:element name="addressLine1">
<xsl:value-of select="*:AddressLine[@sequence='1']" />
</xsl:element>
<xsl:element name="addressLine2">
<xsl:value-of select="*:AddressLine[@sequence='2']" />
</xsl:element>
<xsl:element name="addressLine3">
<xsl:value-of select="*:AddressLine[@sequence='3']" />
</xsl:element>
<xsl:element name="addressLine4">
<xsl:value-of select="*:AddressLine[@sequence='4']" />
</xsl:element>
<xsl:element name="postalCode">
<xsl:value-of select="*:PostalCode" />
</xsl:element>
<xsl:element name="city">
<xsl:value-of select="*:CityName" />
</xsl:element>
<xsl:element name="stateCode">
<xsl:value-of select="*:CountrySubDivisionCode" />
</xsl:element>
<xsl:element name="countryCode">
<xsl:value-of select="*:CountryCode" />
</xsl:element>
</xsl:element>
</xsl:for-each>

Denis MARETTE

Thank you again for your help

I've been trying to apply this to my context but I have to admit that I'm manipulating concepts that I'm still too unfamiliar with to really understand what I'm doing.

I introduced this modification in my code :

<xsl:stylesheet version="2.0" xmlns="">schema.infor.com/.../2" xmlns:expath-zip="">http://expath.org/ns/zip" xmlns:fn="">www.w3.org/.../xpath-functions" xmlns:dns="">schema.infor.com/.../2" xmlns:saxon="">http://saxon.sf.net/" xmlns:expath-file="">http://expath.org/ns/file" xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xmlns:xsl="">www.w3.org/.../Transform" xmlns:exslt-random="">http://exslt.org/random" xmlns:exslt-common="">http://exslt.org/common" xmlns:exslt-math="">http://exslt.org/math" xmlns:xs="">www.w3.org/.../XMLSchema" xmlns:math="">www.w3.org/.../math" xmlns:map="">www.w3.org/.../map" exclude-result-prefixes="xs xsl fn expath-file expath-zip exslt-common exslt-math exslt-random map math saxon xsi ">
<xsl:output method="xml" encoding="UTF-8" indent="no" byte-order-mark="no"/>
<xsl:strip-space elements="*"/>
<xsl:template match="/">
<xsl:if test="/*:SyncSalesOrder">
<xsl:element name="SyncDMSalesOrder5">
<xsl:namespace name="xs" select="'">www.w3.org/.../>
<xsl:if test="/*:SyncSalesOrder/@languageCode">
<xsl:attribute name="languageCode">
<xsl:value-of select="/*:SyncSalesOrder/@languageCode"/>
</xsl:attribute>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/@releaseID">
<xsl:attribute name="releaseID">
<xsl:value-of select="/*:SyncSalesOrder/@releaseID"/>
</xsl:attribute>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/@systemEnvironmentCode">
<xsl:attribute name="systemEnvironmentCode">
<xsl:value-of select="/*:SyncSalesOrder/@systemEnvironmentCode"/>
</xsl:attribute>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/@versionID">
<xsl:attribute name="versionID">
<xsl:value-of select="/*:SyncSalesOrder/@versionID"/>
</xsl:attribute>
</xsl:if>
<xsl:copy-of select="/*:SyncSalesOrder/*:ApplicationArea" copy-namespaces="no" />
<xsl:if test="/*:SyncSalesOrder/*:DataArea">
<xsl:element name="DataArea">
<xsl:copy-of select="/*:SyncSalesOrder/*:DataArea/*:Sync" copy-namespaces="no" />
<xsl:element name="DMSalesOrder5">
<xsl:element name="SalesOrderHeader">
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:DocumentID/*:ID">
<xsl:element name="DocumentID">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:DocumentID/*:ID/text()"/>
</xsl:element>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:Status/*:Code">
<xsl:element name="Status">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:Status/*:Code/text()"/>
</xsl:element>
</xsl:if>
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:DocumentDateTime">
<xsl:element name="DocumentDateTime">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderHeader/*:DocumentDateTime/text()"/>
</xsl:element>
</xsl:if>
</xsl:element>
<xsl:for-each select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:LineNumber/text()">
<xsl:element name="SalesOrderLine">
<xsl:if test="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:LineNumber">
<xsl:element name="LineNumber">
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/*:SalesOrder/*:SalesOrderLine/*:LineNumber/text()"/>
</xsl:element>
</xsl:if>
</xsl:element>
</xsl:for-each>
</xsl:element>
<xsl:value-of select="/*:SyncSalesOrder/*:DataArea/text()"/>
</xsl:element>
</xsl:if>
<xsl:value-of select="/*:SyncSalesOrder/text()"/>
</xsl:element>
</xsl:if>
</xsl:template>
</xsl:stylesheet>

Indeed it starts to produce results closer to those expected but it is not yet tha( (I simplified the exercise by trying to produce only the line numbers of a customer order detail)

The lines are now replicated (4 lines instead of 1 before) but the content still keeps the accumulation of the 4 lines ?

<?xml version="1.0" encoding="UTF-8"?>
<SyncDMSalesOrder5 xmlns="">schema.infor.com/.../2" xmlns:xs="">www.w3.org/.../XMLSchema" languageCode="GB" releaseID="9.2" systemEnvironmentCode="Production" versionID="2.13.5">
<ApplicationArea>
<Sender>
<LogicalID schemeVersionID="16.0.0.050">lid://infor.m3.m3</LogicalID>
<ComponentID schemeVersionID="16.0.0.20210322170048">M3BE</ComponentID>
<ConfirmationCode>OnError</ConfirmationCode>
</Sender>
<CreationDateTime>2021-05-19T13:23:38.935Z</CreationDateTime>
<BODID>8b7191e8-4534-4cb7-a71b-be92961a845d</BODID>
</ApplicationArea>
<DataArea>
<Sync>
<AccountingEntityID>790_AAA</AccountingEntityID>
<LocationID>001</LocationID>
<ActionCriteria>
<ActionExpression actionCode="Replace"/>
</ActionCriteria>
</Sync>
<DMSalesOrder5>
<SalesOrderHeader>
<DocumentID>0010000025</DocumentID>
<Status>Allocated</Status>
<DocumentDateTime>2010-03-23</DocumentDateTime>
</SalesOrderHeader>
<SalesOrderLine>
<LineNumber>1234</LineNumber>
</SalesOrderLine>
<SalesOrderLine>
<LineNumber>1234</LineNumber>
</SalesOrderLine>
<SalesOrderLine>
<LineNumber>1234</LineNumber>
</SalesOrderLine>
<SalesOrderLine>
<LineNumber>1234</LineNumber>
</SalesOrderLine>
</DMSalesOrder5>
</DataArea>

Copyright © 2025 Infor. All rights reserved.