none
All incoming messages fail after receiving a new set of .xsd's RRS feed

  • Question

  • From an external supplier we received a new set of .xsd’s. In the xml disassembler step of the receiving pipeline I removed in the properties all the old document schemas and added the new schemas (allow unrecognized message = false) in the documents schema property.
    After deploying the solution all incoming messages failed!
    Then I removed from the document schema property 2 schemas with root name ‘typeOnlySchema’ (which it seems only contains definitions). After redeployment almost all tests worked but not the following example:
    When bizTalk receives:
    <ID>123456</ID> -> GOOD
    <ID>123456 </ID> -> FAILED, according the definition which is located in the 2 removed files below it should work:

    <xsd:simpleType name="IdentificatiecodeMax50IdentifierType">
      <xsd:annotation/>.......
      <xsd:restriction base="udt:IdentifierType">
        <xsd:maxLength value="50"/>
      </xsd:restriction>
    </xsd:simpleType>
    Where identifiertype is located in the second schema:
    <xsd:simpleType name="IdentifierType">
      <xsd:annotation/>.......
      <xsd:restriction base="xsd:token"/>
    </xsd:simpleType>

    If I add this definition all messages fail, so how can I solve this?
    And why do all messages fail when I add the 2 definition files?
    Sunday, June 28, 2020 7:17 AM

All replies

  • xsd:token -> whitespace replaced and collapsed string

    I didn't use token ever.

    Guess a whitespace within the text is ok but not at begin or end of the string.


    • Edited by Snoopy2016 Sunday, June 28, 2020 1:28 PM
    Sunday, June 28, 2020 1:25 PM
  • The previous version also contained whitespace. And visual studio has no problems with the validation so I don't understand why BizTalk can't handle this.
    Sunday, June 28, 2020 7:39 PM
  • I just tried a simple schema with a xs:Toke and maxLength of 50 and could not reproduce the issue.

    What is the error you are getting?

    If you remove the typeSchema and it has reference to it, I would expect it to fail then, rather than the other way around.   

    Tuesday, June 30, 2020 1:33 AM