Database Connection Point Namespace

Is it possible to specify a namespace on a database connection point? I'm building a BOD from a DB connection point. The ERP I'm sending the BOD to requires the xmlns attribute. I'm not sure how to specify that since all I'm creating is the DataArea portion.

Find more posts tagged with

ION Connect

Accepted answers

All comments

Maxime Richard

Hi,

The database connection point seems to behave the same way as the file connection point : no namespace by default in your custom BOD.

As a workaround, you can add a mapping step in your data flow that will add the namespace of your choice.

Kevin Heiman

You can add the string to the resulting XML before returning it in a number of ways in SQL using .modify , or concat string, or substitute...

-- build out BOD
SET @CHARxxxxBOD = '<xxxxxxBOD xmlns="">schema.infor.com/.../2" xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xsi:schemaLocation="schema.infor.com/.../2 ">schema.infor.com/.../xxxxxBOD.xsd" versionID="2.12.1" releaseID="9.2" systemEnvironmentCode="Production" languageCode="en-US">
<ApplicationArea>

if reading as a variable:

;with XMLNAMESPACES(DEFAULT 'schema.infor.com/.../2' )

Need a little more context as to what you are attempting to do.

Legacy Contributor

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

I wrestled with a very similar issue about a year ago when we were attempting to connect a BOD published by the Infor XA ERP package 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. As Maxime R. stated, this is normal behavior for file connection points and database connection points.

I see that you have been recommended two solutions for your issue, one involving adding a mapping step to your document flow and another involving SQL code to build out the BOD. I personally went the route of adding a "Graphical Mapping" step to our document flow between the database connector element and the final destination element for Infor CRM using ION's built-in Mappings tool . The first step is to use the Graphical Mapper to connect the main node in the "Source" BOD to the main 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 your ERP.

The second hurdle that you will most likely need to overcome is 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 when connecting to any Infor ERP package or any Infor software package. 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 the new function should be saved and verified, the Mapper should be approved, and the document flow should be deactivated, the Mapper should be added to the document flow, and the document flow should be reactivated. Once you do all this, hopefully you will see much better results in the receiving ERP.

I hope you find this information useful.

Copyright © 2025 Infor. All rights reserved.