cancel
Showing results for 
Search instead for 
Did you mean: 

NS0 namespace in every element after mapping

Former Member
0 Kudos

Hi All,

We have a scenario IDOC --> XML file on a file share. I created a free style data type for the XML message and the mapping objects. When I test the message mapping, every XML element gets the ns0 namespace before the tagname. The namespace prefix is ok to be mentioned on a root level, but not with every element. Can we configure something that this behavior is not occuring anymore?

Example current result:

 

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

<ns0:OrderCreateNotification xmlns:ns0="urn:mc-nl:procurement:boras:boras">

<ns0:OrderNumber>4550000037</ns0:OrderNumber>

<ns0:DocumentDate>20140722</ns0:DocumentDate>

<ns0:OrderItem>

     <ns0:ItemNumber>00001</ns0:ItemNumber>

     <ns0:Unit>ST</ns0:Unit>

     <ns0:Quantity>100.000</ns0:Quantity>

     <ns0:NettPrice>10000</ns0:NettPrice>

     <ns0:PurchaseRequisitionItemNumber>00000</ns0:PurchaseRequisitionItemNumber>

     <ns0:TaxRate>21.00</ns0:TaxRate>

</ns0:OrderItem>

</ns0:OrderCreateNotification>

I expected to have it like this:

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

<ns0:OrderCreateNotification xmlns:ns0="urn:mc-nl:procurement:boras:boras">

<OrderNumber>4550000037</OrderNumber>

<DocumentDate>20140722</DocumentDate>

<OrderItem>

     <ItemNumber>00001</ItemNumber>

     <Unit>ST</Unit>

     <Quantity>100.000</Quantity>

     <NettPrice>10000</NettPrice>

     <PurchaseRequisitionItemNumber>00000</PurchaseRequisitionItemNumber>

     <TaxRate>21.00</TaxRate>

</OrderItem>

</ns0:OrderCreateNotification>

With the data type it is possible to define the property "qualify schema", but it doesn't seem to do anything.

I know of the possibility to use the XML Anonimizer module, but I was hoping that we can configure this in a standard way.

kind regards,

Mark

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi All,

Issue was solved by defining the value "None" in the Qualify Schema option + reimporting the message types into the message mapping after making the Qualify Schema change. The XML structures didn't got refreshed automatically.

Everything is working normally now with the ns prefix only on root level.

Regards,

Mark

Answers (1)

Answers (1)

engswee
Active Contributor
0 Kudos

Hi Mark

This looks strange - normally the namespace prefix is only at the root level when defining the Data Type.

Can you please share a screenshot of how your Data Type is defined?

Rgds

Eng Swee

Former Member
0 Kudos

screenshot with data type attached

markangelo_dihiansan
Active Contributor
0 Kudos

Hi Mark,

What are the options for the Qualify Schema?

Regards,

Mark