Managing failed orders in BC/NAV integration

Jon Thorne

Posted on 23/01/2022 22:43:37

I would like to understand what the standard practice is for handling orders that fail to be transferred to the ERP system with the live integration and how this can be managed by the end user. This may happen if the order details do not match some data correctly in the ERP system or something has changed with the products since the last batch update. As I understand any exception to posting the data in NAV or BC would be rejected and not saved in NAV/BC, is that correct? (eg. product blocked or deleted) Is there a notification that can be generated if this happens?

I can see that orders can be filtered to show only "Untransfered" orders. Then there is a button to "Transfer to ERP". How would the user know what the exception was and what would need to be fixed? Is there any way to manage these order transfer exceptions in BC/NAV?

Any comments on how others manage this process would be helpful. Thanks.

Replies

Dmitriy Benyuk

Posted on 24/01/2022 09:34:23

Hi Jon,

in the Live Integration there is an event fired when the order was sent to ERP: OnAfterSendingOrderToErp.
It contains the error message if there was an error during export of the order. So you can implement your custom stuff what to do in case of errors.

You can enable logging in the LiveIntegration settings page and then in the LiveIntegration log file you can find why the order sending was failed.
The similar error information is also stored on the Order Log list when you open the failed order in the Ecommerce and click a show log button from there.

Also you can create a scheduled task in the Integration framework Batch using the "Sync queued orders using Live Integration" addin that can export not exported orders to the ERP.
You can read more about this addin here.
Hope that can help

BR, Dmitrij

Jon Thorne

Posted on 01/02/2022 11:09:11

Hi Dmitrij,

Thank you for helping out with my query. From what you have described there are many ways to customise the order sending process and create logs to check for error messages. What I was equiring about is if there was a standard process for the user (not system admin) to do this using the ecommerce admin interface without having to scan through system log files. Yes, I can see that there is a was to manually send the order again, or reprocess it automatically. But that will not help if there is no easy way to see what the error is, as it will just error again. For instance if a product or customer is blocked after the cart is created and the order is processed this will just get stuck. If there is no "standard" way to handle this, then we will have to implent something ourselves that will make it as easy as possible for the customer to understand and fix.

I am also curious about the section you mentioned about queued orders. This seems to be must have functionality if there are connection issues to the ERP. But from the title of this section is seems that this only works on AX, not NAV or BC. "QUEUED ORDERS (AX ONLY)". This is not mentioned in the description, is it correct? Or is there another method for BC/NAV?

https://doc.dynamicweb.com/documentation-9/integration/integration-framework-2/live-integration#sideNavTitle1-5

Regards, Jon.

Dmitriy Benyuk

Posted on 02/02/2022 11:46:39

This post has been marked as an answer

Hi Jon,
The "Sync queued orders using Live Integration" add-in can also work with the BC/NAV.
It is mentioned here.

You can also configure the notifications by email:

BR, Dmitrij

Votes for this answer: 1

You must be logged in to post in the forum

Developer forum

Managing failed orders in BC/NAV integration

Replies