Sending (or retrieving) import errors

Integrator.io
, , , ,
1

Hi again!

I'm wondering if it's possible to send or retrieve NetSuite import errors.

If an error occurs we can see it somewhere else other than the Integrator dashboard. Elastic's Kibana, for example.

Thanks!

2

There are 3 different ways to do this, and it really comes down to personal/technical preferences.

  1. You can use a response mapping to add the 'errors' back into the source record payload, and then you would add a new bubble to the end of your flow that sends the errors to the external API just like you would send any other data to an API, and you would use the mapper and/or the AFE to only send the 'errors' data, etc... I added some screen shots from one of my flows that does a similar pattern of sending data/errors to splunk at the end of the flow.
  2. You can send the errors directly from a postSubmit hook script in your NetSuite import bubble. From a postSubmit hook script, you can use the 'integrator-api' module and then invoke a virtual import from your script to send data to any API endpoint, etc... The postSubmit hook is given all the errors from the import, etc...
  3. You can build a new standalone 'delta' flow that uses the integrator.io API to retrieve errors from other flows. The source bubble in this new standalone flow would use the integrator.io API itself. Please see here and here for more info on the API.

5301043caa20740200000001-3518dc6d249247b68ce47bde6598362b.png
5301043caa20740200000001-3518dc6d249247b68ce47bde6598362b.png2560×657 151 KB

5301043caa20740200000001-3479a7ca77ed46f7966f123778774e1f.png
5301043caa20740200000001-3479a7ca77ed46f7966f123778774e1f.png2423×1253 139 KB

5301043caa20740200000001-a2a8e30e576d41ccb32c7b5b6d5167a0.png
5301043caa20740200000001-a2a8e30e576d41ccb32c7b5b6d5167a0.png1420×878 78.2 KB

3

Thanks again, Scott, for the very detailed response!

I'll give it a go.

4

I'm trying to do something similar only I was hoping to import an error message from a response into NetSuite. I have a NetSuite Export then https:// Lookup and then a NetSuite Import. Is there a way for me to get the error from the response from the https:// request and then import it to a field on the record I'm mapping data to in NetSuite? It's the errors that happen in the Lookup response that I want to capture on the record I'm updating in NetSuite.

5

Hey Gus, what you are trying to do is exactly what I outlined in #1 above. Be sure to set the following as well in your flow. Cheers!

5301043caa20740200000001-3537501bb0ab4de1a49068e081a0043b.png
5301043caa20740200000001-3537501bb0ab4de1a49068e081a0043b.png1598×522 51.2 KB

5301043caa20740200000001-6273406df73746af9f380ca888d24560.png
5301043caa20740200000001-6273406df73746af9f380ca888d24560.png1114×526 38.7 KB

6

5301043caa20740200000001-6ee6767896cc409792c1e182d0e0358d.png
5301043caa20740200000001-6ee6767896cc409792c1e182d0e0358d.png1616×425 24.4 KB

I can set up the results mapping with a data an errors object shown above. I have the option to proceed regardless set after my lookup. However when I look at my mapping for my NetSuite import I don't see the errors array.

5301043caa20740200000001-f209ee4c07464aaf830b8eb9727f35d7.png
5301043caa20740200000001-f209ee4c07464aaf830b8eb9727f35d7.png1647×550 48.7 KB

7

It is not showing in the sample input because the particular record being used as the sample did not return an error when it ran the preview for the lookup before it, etc...

This is easy to work around, and you can manually add the ioErrors field to the input panel. The input panel is fully editable for the purpose of typing and testing different scenarios on the fly. You can also add the field mapping without the field being in the input, and this is really common to map fields that are not in the sample input, but will eventually be encountered for some data being processed, and again, the input panel lets you type and test any scenario that you want to support on the fly.