Error Handling in 2006

Home Page Forums BizTalk 2004 – BizTalk 2010 Error Handling in 2006

Viewing 1 reply thread
  • Author
    Posts
    • #14835

      Thanks for the new feature, it becomes easy to deal with the suspended queue. But still i got a question.

      In a receive port A, I checked the option \”Generate error report for failed message\”

      And then create another send port B to subscribe to A, but only send errors:
      Filter:
      ErrorReport.ReceivePortName==A And
      ErrorReport.FailureCode Exists

      When i delete a start tag in the file, the error handling function is fine, send the file to a folder instead of suspended queue.

      But if i omitted a mandatory (minOccur=1, maxOccur=1) element, the file went through to destination folder without errors even though the validation should fail.

      What should i do to catch missing mandatory field error?

      Thanks for any advice.

    • #14836

      Do you have a custom receive pipeline that includes the Xml Validator component. This component is not included in the standard XmlReceive pipeline.
      Without this component the message is never validated against its schema.
      The XmlDisassembler only checks for well-formedness – all tags match, no erroneous characters, etc.

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