Skip to content
+1-888-319-3663

COMMUNITY FORUM

XML File Destination

Scott asked 7 years ago
I working on an integration with a destination of XML File. When creating the XML File Format the name field does not appear to accept numbers. For example, one of the Element Names is UD1. When I attempt to type this name in SmartConnect I only get UD. In this node alone there is UD1-UD14. Is this a bug? Or on purpose? Is there a work around or configuration option I am missing? We are using version 20.13.0.49. Thanks, Scott
Answers
Best Answer
kevin answered 7 years ago
Scott,

That appears to be an oversight, and over zealous character checking. I will send it to our developers for a fix.

The workaround is to create your xml file in a text file and then load it into the xml destination using the Xml file lookup at the top of the XML file format window.

e.g. this xml below loads correctly.
<test>
  <node>
    <UD1 />
    <UD2 />
    <UD3 />
  </node>
</test>

kevin answered 7 years ago
Scott,

That appears to be an oversight, and over zealous character checking. I will send it to our developers for a fix.

The workaround is to create your xml file in a text file and then load it into the xml destination using the Xml file lookup at the top of the XML file format window.

e.g. this xml below loads correctly.
<test>
  <node>
    <UD1 />
    <UD2 />
    <UD3 />
  </node>
</test>

Scott replied 7 years ago

Thank you for the confirmation. It also appears that when creating an attribute the Name cannot be lower case. My end result schema calls for the following

When I go to create the xml file with an attribute of ‘xmlns’ I get the error ‘Could not write to export file : The namespace declaration attribute has an incorrect ‘namespceURI’:”.

If I change the name field to ‘XMLNS’ then the file produces without issue, however the API engine I am feeding the xml file to will not read the uppercase.

Thanks,
Scott

Scott replied 7 years ago

Here is the line missing from the above post


If you would like to submit an answer or comment, please sign in to the eOne portal.