The Web Services Adapter does not interpret a row error as unsuccessful.

There is a queue-based integration that sends sales orders to AX 2012 using the Web Services Adapter.  The user is trying to use DTS Flow Control “Success (0)” to send a message to the Retry or DeadMessage queue when a row fails to insert/create/update into AX, but it’s not working.  The Web Services interprets the row error as a successful transaction.  How do you get the DTS to recognize the row error as a failure?

When using the Web Services Adapter, Flow Control methodology alone does not support sending XML message to different queues when there is a row failure.   The web service sends a request, receives a response, and interprets this as Success(1).  The Web Services Adapter does recognize the row error, but still considers the call to the Web Service method to be successful.

To trap for row errors and send the XML message to another message queue, use a Pre-Operation step that tests the Scribe GetRowError() function.  If true, call the EndJobFailed() function as shown below:

IF(ISERROR(GETROWERROR()  ) , TRUE( ), ENDJOBFAILED( ) )

The Web Services Adapter does not interpret a row error as unsuccessful.