Example code for using IONApiRef to extract data from XML

Hi,

I need help in using IONApiRef to extract parts of an XML from a BOD and send it as Input Body in "ION API Connection Point"->Send to API.

My source XML has [CDATA] in an element and I am using the below mapping in Input Body tab->Map input document to API request field. When I test the API, the data in this element does not get sent with the body, however, the non-CDATA elements do get sent in the body of the API call. How can I get this to work?

Source XML:

<SyncWSLS3Msg><DataArea><WSLS3Msg> <DocumentID><ID></ID></DocumentID> <Message><![CDATA[*** some important data to send to API here *** ]]></Message> </WSLS3Msg></DataArea></SyncWSLS3Msg>

Below is the mapping example:
 <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <Body> <Message><IonApiRef>SyncWSLS3Msg/DataArea/WSLS3Msg/Message</IonApiRef></Message> <DocID><IonApiRef>SyncWSLS3Msg/DataArea/WSLS3Msg/Document/ID</IonApiRef></DocID> </Body>

Find more posts tagged with

ION Connect

Accepted answers

Legacy Contributor

Hi, figured this one out.

The XSLT function text() should be able to pick up the CDATA from the elements using IONApiRef like so:

<IonApiRef>SyncWSLS3Msg/DataArea/WSLS3Msg/Message/text()</IonApiRef>

All comments

Legacy Contributor

Hi, figured this one out.

The XSLT function text() should be able to pick up the CDATA from the elements using IONApiRef like so:

<IonApiRef>SyncWSLS3Msg/DataArea/WSLS3Msg/Message/text()</IonApiRef>

Maxime Richard

Greetings,

Speaking of IONApiRef, is it possible to do a mapping by concatenating 2 attributes from an input document ?

For instance, i am using a RawData CustomBOD to upload a .pdf document in IDM that has been dropped in a folder.

This mapping below is working by manually adding an extension to the file name. But i get an error 400 returned by the API because the file has no extension (.pdf ...). Below the input body requested by the API :

<?xml version="1.0" encoding="UTF-8" ?>

<item xmlns="http://infor.com/daf">
<attrs>
<attr>
<name>MDS_Status</name>
<value>20</value>
</attr>
<attr>
<name>MDS_Name</name>
<value><IonApiRef>SyncMyRawDataFile/DataArea/MyRawDataFile/@FileName</IonApiRef></value>
</attr>
</attrs>
<resrs>
<res>
<filename><IonApiRef>SyncMyRawDataFile/DataArea/MyRawDataFile/@FileName</IonApiRef></filename>
<base64><IonApiRef>SyncMyRawDataFile/DataArea/MyRawDataFile/RawData</IonApiRef></base64>
</res>
</resrs>
<acl>
<name>Public</name>
</acl>
<entityName>MDS_File</entityName>
</item>

I need to add attribute /MyRawDataFile/@FileExtension to /MyRawDataFile/@FileName with a "." between them to get a full acceptable name for the document to upload in IDM.

The RawData BOD :

<SyncMyRawDataFile releaseID="9.2">
<ApplicationArea>
<Sender>
<LogicalID>infor.file.test_pdf_idm_recuperationdemec</LogicalID>
<ComponentID>External</ComponentID>
<ConfirmationCode>OnError</ConfirmationCode>
</Sender>
<CreationDateTime>2019-07-17T15:37:19.843Z</CreationDateTime>
<BODID>1563377839843:d98c5bae-82e7-4288-b83d-2498a11c2898</BODID>
</ApplicationArea>
<DataArea>
<Sync>
<AccountingEntityID/>
<LocationID/>
<ActionCriteria>
<ActionExpression actionCode="Replace"/>
</ActionCriteria>
</Sync>
<MyRawDataFile FileName="myFileName" FileExtension="pdf" FilePath="Test_pdf">
<DocumentID>RD-1509747869-1563377839843</DocumentID>
<RawData>...</RawData>
</MyRawDataFile>
</DataArea>
</SyncMyRawDataFile>

What do you think of this ?

Legacy Contributor

I do not think you can use IonApiRef twice to load one field. Best way to do this would be to have an additional mapping step where you can concatenate two fields that are already extracted via IonApiRef and manipulate it to include a "." in between and so on.

The thought of directly mapping/ concatenating two or more IonApiRef outputs to form a final output is fascinating. But then we would run into supporting multiple type of data type based operations (like concatenate for string, math functions for number, logic functions for boolean, date operators on date fields). This is what we can already do with ION Mapper. So its best to form the final value you want from multiple IonApiRefs in the additional mapper step.

Maxime Richard

Thank you for your answer Vignesh. As a workaround, i added a workflow in the document flow to change the value of some tags of the incoming document by using "set parameter" step.

Copyright © 2025 Infor. All rights reserved.