ION Database Connector stripping majority of namespace portion of BOD

eric-masson

Greetings to the ION community,

I am wondering if anyone else has encountered a similar issue to the one that we are facing with the use of a database connector.  We are also seeing an issue with logical ID, however, the much bigger issue is the fact that ION is stripping off almost the entire “namespace” at the top of the BOD when a BOD passes through our database connector.

A little additional background, we are enhancing the Infor CRM to XA integration by extending Sync.SalesOrder to include Order Line Item Comments.  The standard integration includes order comments, not the order line item comments.  In our testing, all looks fine with the stored procedure and the data is being sent from XA to ION.  Unfortunately, CRM is unable to receive the data due to the stripping of data in the namespace portion of the BOD.

We have been working with the CRM and Infor OS support teams.  Today's update from Infor OS was that "this is working by design".

Here's a look at what is happening (see below)... any thoughts or comments from the community would be greatly appreciated.  Thank you in advance!

 

     Before passing through the database connector, the “namespace” portion of the BOD looks like this:

<?xml version="1.0" encoding="UTF-8"?><SyncSalesOrder xmlns="http://schema.infor.com/InforOAGIS/2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schema.infor.com/2.10.0/InforOAGIS/BODs/Developer/SyncSalesOrder.xsd" versionID="2.10.0" systemEnvironmentCode="Production" releaseID="9.2" languageCode="en-US">

     After passing through the database connector, very little remains from the original “namespace”:

<SyncSalesOrder releaseID="9.2">

 

Legacy Contributor

Hello, Stephanie.  I hope that all is well with you and that you are staying healthy and safe during these difficult times.

I wrestled with this very same issue regarding connecting a BOD published by Infor XA and sent to Infor CRM with a database connector in the middle of the document flow.  Working with Infor ION Support, they explained to me why a database connector strips away the majority of the "namespace" portion of a BOD.  I remember not liking what I heard, but I also remember that it made complete sense why this was happening.

So, what to do?  A "Graphical Mapping" element using the ION Mappings tool needs to be set up between the database connector element in the document flow and the final destination element for Infor CRM.  The first step is to use the Graphical Mapper to connect the main Sync.SalesOrder node in the "Source" BOD to the main Sync.SalesOrder node in the "Target" BOD.  ION will automatically begin creating any necessary direct connections between the sub nodes of the Source BOD and the Target BOD.   If you look at the "XSLT Editor" tab, you will see that ION generated a LOT of XSLT code in the stylesheet it created.  My understanding is that this will help you produce a much more complete "namespace" portion in the "Target" BOD that will be sent to Infor CRM.

The second step is to overcome the fact that a generic Graphical Mapping will not retain the original BOD's LogicalID due to the database connector.  And this will be a problem for CRM.  To overcome this issue, the Graphical Mapping will need a new function set up for the LogicalID node using the "Function Modeler".  This new function will most likely be a "Cast to Normalized String" function that contains the correct value of the LogicalID as a constant value.

Once both of these steps have been performed, the XSLT for new function has been saved and verified, the Mapper has been approved, and the document flow deactivated, updated and reactivated, you should see much better results in CRM.

I hope you find this information useful.