New Custom Bod Missing Root Element when Written to outbound connection point

unknown

I'm developing a very simple new xml definition. If flows from an LX App connection to an ftp file connection. Oneview shows the document as a complete bod with the root definition.  However, when ION writes to the output connection, the root element gets stripped from the document. 

Below is what oneview shows going to the destination ftp connection with the root as 'SyncXSource'

<?xml version="1.0" encoding="UTF-8"?>
<SyncXSource releaseID="9.2" versionID="2.5.1" xmlns:xsi="">www.w3.org/.../XMLSchema-instance">
<ApplicationArea>
<Sender>
<LogicalID>lid://infor.lx.as400tst-bpcsec</LogicalID>
<ComponentID>ERP</ComponentID>
<ConfirmationCode>OnError</ConfirmationCode>
</Sender>
<CreationDateTime>2022-12-28T16:11:09Z</CreationDateTime>
<BODID>infor-nid:Test:::AF82C01351:202212281011096944?XSource&amp;verb=Sync</BODID>
</ApplicationArea>
<DataArea>
<Sync>
<TenantID>Test</TenantID>
<ActionCriteria>
<ActionExpression actionCode="Replace"/>
<ChangeStatus>
<Code/>
<Description/>
<EffectiveDateTime>2022-12-28T16:11:09Z</EffectiveDateTime>
<ReasonCode/>
<Reason/>
<StateChange>
<FromStateCode/>
<ToStateCode/>
<ChangeDateTime>2022-12-28T16:11:09Z</ChangeDateTime>
<Description/>
<Note/>
</StateChange>
</ChangeStatus>
</ActionCriteria>
</Sync>
<XSource>
<HEADER>
<MAR_ORDER>S0691901-001-640164</MAR_ORDER>
<HOU_ORDER>1533958</HOU_ORDER>
<MACH_NUMBER>CF100K6/01533958</MACH_NUMBER>
<SERIAL_NUMBER variationID="202212281011096944" lid="lid://infor.lx.as400tst-bpcsec">AF82C01351</SERIAL_NUMBER>
<SCHED_DATE>20221229</SCHED_DATE>
</HEADER>
<DETAIL>
<LINE>1</LINE>
</DETAIL>
</XSource>
</DataArea>
</SyncXSource>

Below shows what ends up in the target destination connection: The root called XSource is missing.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ApplicationArea>
<Sender>
<LogicalId>lid://infor.lx.as400tst-bpcsec</LogicalId>
<ComponentID>ERP</ComponentID>
<ConfirmationCode>OnError</ConfirmationCode>
</Sender>
<BODId>infor-nid:Test:::AF82C01351:202212280940059028?XSource&amp;verb=Sync</BODId>
<CreationDateTime>2022-12-28T15:40:05Z</CreationDateTime>
</ApplicationArea>
<DataArea>
<HEADER>
<MAR_ORDER>S0691901</MAR_ORDER>
<HOU_ORDER>1533958</HOU_ORDER>
<MACH_NUMBER>CF100K6/01533958</MACH_NUMBER>
<SERIAL_NUMBER>AF82C01351</SERIAL_NUMBER>
<SCHED_DATE>20221229</SCHED_DATE>
</HEADER><DETAIL>
<LINE>1</LINE>
</DETAIL>
</DataArea>

I've looked at this for hours and cannot figure out when the root element gets stripped from the document. I've done dozens of document flows like this and never had this issue.

Thanks to anyone who has a suggestion.

Danil Klemeshov

Hello,

I tried to reproduce your case; however, in my case, everything works well. 

I did the following:
1. Created a File Template based on your example. But I removed this part from the header tag: "versionID="2.5.1" xmlns:xsi="">www.w3.org/.../XMLSchema-instance">". So my XML looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<SyncXSource releaseID="9.2">
<ApplicationArea>
<Sender>
<LogicalID>lid://infor.lx.as400tst-bpcsec</LogicalID>
<ComponentID>ERP</ComponentID>
<ConfirmationCode>OnError</ConfirmationCode>
</Sender>
<CreationDateTime>2022-12-28T16:11:09Z</CreationDateTime>
<BODID>infor-nid:Test:::AF82C01351:202212281011096944?XSource&amp;verb=Sync</BODID>
</ApplicationArea>
<DataArea>
<Sync>
<TenantID>Test</TenantID>
<ActionCriteria>
<ActionExpression actionCode="Replace"/>
<ChangeStatus>
<Code/>
<Description/>
<EffectiveDateTime>2022-12-28T16:11:09Z</EffectiveDateTime>
<ReasonCode/>
<Reason/>
<StateChange>
<FromStateCode/>
<ToStateCode/>
<ChangeDateTime>2022-12-28T16:11:09Z</ChangeDateTime>
<Description/>
<Note/>
</StateChange>
</ChangeStatus>
</ActionCriteria>
</Sync>
<XSource>
<HEADER>
<MAR_ORDER>S0691901-001-640164</MAR_ORDER>
<HOU_ORDER>1533958</HOU_ORDER>
<MACH_NUMBER>CF100K6/01533958</MACH_NUMBER>
<SERIAL_NUMBER variationID="202212281011096944" lid="lid://infor.lx.as400tst-bpcsec">AF82C01351</SERIAL_NUMBER>
<SCHED_DATE>20221229</SCHED_DATE>
</HEADER>
<DETAIL>
<LINE>1</LINE>
</DETAIL>
</XSource>
</DataArea>
</SyncXSource>

2. Created an Object Schema based on the Template.
3. Created SFTP connection point with two (read and write) scenarios for the Sync.XSource Document. 
4. Created and Activated a simple DocumentFlow with two "FileSteps".

My result file is: 
<?xml version="1.0" encoding="UTF-8"?>
<SyncXSource releaseID="9.2">
<ApplicationArea>
<Sender>
<LogicalID>lid://infor.lx.as400tst-bpcsec</LogicalID>
<ComponentID>ERP</ComponentID>
<ConfirmationCode>OnError</ConfirmationCode>
</Sender>
<CreationDateTime>2022-12-28T16:11:09Z</CreationDateTime>
<BODID>infor-nid:Test:::AF82C01351:202212281011096944?XSource&amp;verb=Sync</BODID>
</ApplicationArea>
<DataArea>
<Sync>
<TenantID>Test</TenantID>
<ActionCriteria>
<ActionExpression actionCode="Replace"/>
<ChangeStatus>
<Code/>
<Description/>
<EffectiveDateTime>2022-12-28T16:11:09Z</EffectiveDateTime>
<ReasonCode/>
<Reason/>
<StateChange>
<FromStateCode/>
<ToStateCode/>
<ChangeDateTime>2022-12-28T16:11:09Z</ChangeDateTime>
<Description/>
<Note/>
</StateChange>
</ChangeStatus>
</ActionCriteria>
</Sync>
<XSource>
<HEADER>
<MAR_ORDER>S0691901-001-640164</MAR_ORDER>
<HOU_ORDER>1533958</HOU_ORDER>
<MACH_NUMBER>CF100K6/01533958</MACH_NUMBER>
<SERIAL_NUMBER variationID="202212281011096944" lid="lid://infor.lx.as400tst-bpcsec">AF82C01351</SERIAL_NUMBER>
<SCHED_DATE>20221229</SCHED_DATE>
</HEADER>
<DETAIL>
<LINE>1</LINE>
</DETAIL>
</XSource>
</DataArea>
</SyncXSource>

I am attaching the file template that I used, please try to use it. 

Kind regards,
Danil.

[View:/cfs-file/__key/communityserver-discussions-components-files/73/DK_5F00_XSource_5F00_Test.xml:320:240]