When I open a XML, sometime for the same XML, Connect Data Mapper add a prefix OLPREFIX-1. When a attach a xml for data, the data is not always loaded correctly because the prefix is present in the mapper. Also, if I do not rename the field in extraction and add it in the form, I have an error on the naming because the : is part of the name.
My use case is to use a DataSet from .NET as XML, load in Connect, print a page. Simple!
Hello Santastp,
Connect has a full support for XML including namespaces, and according to my understanding of XML namespaces, having a prefix to qualify the local elements as part of that namespace is a requirement.
So this happens when you have a namespace (xmlns:“http://www.example.com/blah”) that does not have a local prefix defined. So you have two choices: Either remove the namespaces (if you’re only using one, that shouldn’t be a problem) or add a prefix to it, such as .
As far as I understand it, this is the “appropriate” way of dealing with non-prefixed namespaces in XML parsers. Of course, not every parser does this, and not every parser supports XML properly anyways…
And, obviously, you could just include the namespace in your data model scheme in Designer also. This won’t affect output, only handling data mapping configurations and fields in the Designer.