Namespace on Source Message in Map from Combined Schemas

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Namespace on Source Message in Map from Combined Schemas

Viewing 1 reply thread
  • Author
    Posts
    • #20801

      The source message in my map was created automatically by BizTalk when I selected 2 schemas as the source from an Orchestration. This is what I end up with:

       

      <Root>

      <MessagePart_1>

         <MySchema1>

         </MySchema1>

      </MessagePart_1>

      <MessagePart_2>

         <MySchema1>

         </MySchema1>

      </MessagePart_2>

      </Root>

      This in itself is not an issue when working with the mapping functions. It becomes a problem when I need to write an XSLT template. BizTalk prefixes each MessagePart with a namespace identifier (ns0 for example). The problem is I don’t know ahead of time what this namespace prefix is going to be and there is no easy way to determine what it will be. When I have only a single schema, it’s easy, I just dump the inbound message to file. I can’t do the same with this combined message…

       

      Has anyone else ran into this issue? Do you have a way to determine what the prefix is going to be.

    • #20802

      If the BizTalk mapper shows ns1 as a prefix on the inbound schema for MessagePart_1 then s1 will end up being the namespace prefix on the inbound message. Not sure why the n gets dropped, but the outbound message ends up using the ns* prefix.

       

      Hope that helps.

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.