In 6.5, I’ve got an xml document setup in trading networks. Document identification seems to work fine. However, extracting values from the document fails whenever the namespace prefixes are different than what is declared on the namespace tab.
For example, let’s say I’ve got document INVOICE with a root node of invoiceroot and have defined the namespaces on the namespace tab using abc=http://document/version1. When an INVOICE comes in, it is recognized because it has the invoiceroot as the root node. However, this incoming document uses a different namespace prefix. For example, 123=http://document/version1. At this point, it seems TN can’t query the document to extract attributes like senderID because the queries for the document type were built off of a namespace of abc. In legal xml, the namespace prefixes can be anything and I need TN to be able to accept all variations of the namespace prefixes since they would still fit the namespace standard. Does anyone know of a solution or a workaround?