SOAPProcessingException: Insert Aborted : Error during insert

[haider3]

Hi Everyone,

I am doing Soap integration with a 3rd party tool. First time they are able to insert record in the import set table. But after that if they try to insert the record with same incident number in Import set table, then we are getting the following error.

When i delete the previous record from Import Set table, then again it works fine. I don't understand what is happening.

If anyone has faced the same issue, please help me out here. Its an uregtn requirement.

Thanks in advance,

Haider

[Alikutty A]

Have you verified the SOAP request data send from the external system?

Does the same error occur when you send the request twice from SOAP UI or any other tools?

Thanks

PS: Hit like, Helpful or Correct depending on the impact of the response

[haider3]

Yes, it occurs when the request from external soap comes twice. First time the record gets inserted but when we are trying to insert the same incident with some updated info in the import set table then it is throwing this error.

[James_Neale · Accepted solution]

Have you checked the System Logs? I've seen this issue a couple of times and it's usually data policies, aborting business rules, or duplicate sys_ids. Note that you'll probably only see the duplicate sys_id issue in the system logs.

Also, you can try running an onAfter script to log the error (note you may want to modify this to be more detailed):

var source = 'SOAP Incident';
if (target.getLastErrorMessage()) {
   gs.log(target.getLastErrorMessage(), source);
} else if (target.isActionAborted()) { // From Fuji Patch 3
   gs.log('Action was aborted by external means e.g. business rule', source);
}

Failing that, download Xplore from Share (or use a background script) to try to replicate the issue. Insert a glide record, get the record and then try updating it. This could be long winded but you can turn on logging to get the business rule output, etc.

Hope that helps