Forum Discussion
apontier
14 years agoOccasional Contributor
Further testing with these strings uncovered that the bug exists when there is an embedded namespace declaration within the CDATA XML elements.
This string fails to parse:
<ECM_Request xmlns="http://www.oneshield.com/DragonSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ExternalDocumentUUID>82A63A48F4F9CF2DE040010ABB9C7CA2</ExternalDocumentUUID></ECM_Request>
whereas this string parses just fine
<ECM_Request><ExternalDocumentUUID>82A63A48F4F9CF2DE040010ABB9C7CA2</ExternalDocumentUUID></ECM_Request>
S the question is - is this a bug with the property transfer or is the only way to do this via a script?
This string fails to parse:
<ECM_Request xmlns="http://www.oneshield.com/DragonSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ExternalDocumentUUID>82A63A48F4F9CF2DE040010ABB9C7CA2</ExternalDocumentUUID></ECM_Request>
whereas this string parses just fine
<ECM_Request><ExternalDocumentUUID>82A63A48F4F9CF2DE040010ABB9C7CA2</ExternalDocumentUUID></ECM_Request>
S the question is - is this a bug with the property transfer or is the only way to do this via a script?