- This topic has 1 reply, 1 voice, and was last updated 9 years ago by
.
-
Posts
-
-
Basically, i’m trying to promote the concatenation of two fields with a comma in between them for use in a correlation set. The line in question is
<b:property name=”ns0:MessageID” xpath=”concat(/*[local-name()=’e537′ and namespace-uri()=”]/*[local-name()=’b2bBody’ and namespace-uri()=”]/*[local-name()=’mE537OrderNims’ and namespace-uri()=”]/*[local-name()=’orderHeader’ and namespace-uri()=”]/*[local-name()=’estimateNumber’ and namespace-uri()=”], ‘,’, /*[local-name()=’e537′ and namespace-uri()=”]/*[local-name()=’b2bBody’ and namespace-uri()=”]/*[local-name()=’mE537OrderNims’ and namespace-uri()=”]/*[local-name()=’orderHeader’ and namespace-uri()=”]/*[local-name()=’supplierReferenceNumber’ and namespace-uri()=”])” />
This however throws an error from the disassemble stage in the pipeline.
Is what i’m trying to do even possible, or have i just got the syntax wrong?
Thanks for any help
-
I also need a promoted property that is not a simple element value, it is the name of the first child element. So I have tried to promote the property by hand in the schema file, and get the same error when the XmlReceive pipeline executes. The annotation in the root element of the BizTalk schema:
<b:property name=”ns0:MessageType” xpath=”/*[local-name()=’SIF_Message’ and namespace-uri()=’http://www.sifinfo.org/uk/infrastructure/2.x’%5D/node()%5B1%5D/local-name()”/>
The xpath is totally valid in xmlspy. It is almost as if the XMLDisassembler component will not allow you to have hacked in your own xpath in the schema, even though I have a valid xpath statement, and the annotations in the schema look ok. I don’t really want to use a custom pipeline component or a map, as it seems as if I should be able to achieve what I need without yet another BizTalk artefact.
Hope we get an answer!
Rob Potter
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.