Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Interface error handling techniques

Former Member
0 Likes
388

Hi,

We have inbound and outbound interfaces.

Please suggest error handling techniques which can be used in inbound/outbound interfaces.

eg: If there is a inbound interface running and uploading file. Now if program terminates in between due to any reason, then how will be come to know that how many records are already uploaded so that when that interface is run again, it should not reload those records..

This is one such example.

Regards,

Ashish Gupta

1 ACCEPTED SOLUTION
Read only

ThomasZloch
Active Contributor
0 Likes
333

I am not writing essays here on general error handling, but for your specific inbound creation example I suggest following logic:

- check for existing object via unique key

- if found, skip further processing and continue with next object

- if not found, create new object

- COMMIT WORK

- continue with next object

You can run this as often as desired until everything has been created.

1 REPLY 1
Read only

ThomasZloch
Active Contributor
0 Likes
334

I am not writing essays here on general error handling, but for your specific inbound creation example I suggest following logic:

- check for existing object via unique key

- if found, skip further processing and continue with next object

- if not found, create new object

- COMMIT WORK

- continue with next object

You can run this as often as desired until everything has been created.