none
Subdocument message order? RRS feed

  • Question

  • When receiving a message that was a subdocument by use of the multiple variant of the schema, is there any way when the individual orchestrations receive the subdocument for them to know what order the subdocument was created in?

    A messy way I thought of doing it was to write a pipeline that would somehow annotate the subdocument at each boundary, but that feels wrong

    I was hoping that there was a property somewhere in the message (or in the message database) that would reveal it.

    If it helps, Im doing this with an 837

    Thursday, January 29, 2015 1:18 AM

Answers

  • With respect to Ordered Delivery scenarios, you don't have to do anything.

    The messaging engine will preserve the order of all messages debatched in the Dissassembly Stage of the Pipeline.  This is a feature of Pipeline processing so order is preserved with any Disassembler, Xml, Flat File or other.

    Meaning, if you process the individual 837 Xml messages using a Sequential Convoy, they will get processed in the order they appear in the EDI.

    Additionally, you can find the position in which the message appeared by reading BTS.InterchangeSequenceNumber.
    • Edited by Johns-305MVP Thursday, January 29, 2015 2:36 AM
    • Proposed as answer by DPS Bali Thursday, January 29, 2015 6:54 AM
    • Marked as answer by Angie Xu Tuesday, February 3, 2015 2:18 AM
    Thursday, January 29, 2015 1:47 AM