Example 1 - Path - Basic splitting logic

  1. Input Purchase Order with MessageID = 123456789 and this simplified structure:
    <SyncPurchaseOrder>
    	<ApplicationArea> … </ApplicationArea>
    	<DataArea>
    		<Sync> … <Sync>
    		<PurchaseOrder>
    			<PurchaseOrderHeader> … </PurchaseOrderHeader>
    			<PurchaseOrderLine> … </PurchaseOrderLine>(1)
    			<PurchaseOrderLine> … </PurchaseOrderLine>(2)
    			<PurchaseOrderLine> … </PurchaseOrderLine>(3)
    		</PurchaseOrder>
    	</DataArea>
    </SyncPurchaseOrder>
    
  2. Configured to split at this line:

    SyncPurchaseOrder/DataArea/PurchaseOrder/PurchaseOrderLine

  3. These three instances of <PurchaseOrderLine> element are found:
    • Document with MessageID = 123456789:1 and this simplified structure:
      <SyncPurchaseOrder>
      	<ApplicationArea> … </ApplicationArea>
      	<DataArea>
      		<Sync> … <Sync>
      		<PurchaseOrder>
      			<PurchaseOrderHeader> … </PurchaseOrderHeader>
      			<PurchaseOrderLine> … </PurchaseOrderLine>(1)
      		</PurchaseOrder>
      	</DataArea>
      </SyncPurchaseOrder>
      
    • Document with MessageID = 123456789:2 and this simplified structure:
      <SyncPurchaseOrder>
      	<ApplicationArea> … </ApplicationArea>
      	<DataArea>
      		<Sync> … <Sync>
      		<PurchaseOrder>
      			<PurchaseOrderHeader> … </PurchaseOrderHeader>
      			<PurchaseOrderLine> … </PurchaseOrderLine>(2)
      		</PurchaseOrder>
      	</DataArea>
      </SyncPurchaseOrder>
      
    • Document with MessageID = 123456789:3 and this simplified structure:
      <SyncPurchaseOrder>
      	<ApplicationArea> … </ApplicationArea>
      	<DataArea>
      		<Sync> … <Sync>
      		<PurchaseOrder>
      			<PurchaseOrderHeader> … </PurchaseOrderHeader>
      			<PurchaseOrderLine> … </PurchaseOrderLine>(3)
      		</PurchaseOrder>
      	</DataArea>
      </SyncPurchaseOrder>