Data Loader - Which Line Failed

Integrator.io
, , ,
1

I am importing transactions into NetSuite using the Data Loader, I have 51 error. I want to know though how do I see which line failed, other than going into the Retry Data that is?

2

Hi @rhysgottwald - It looks like you have an open Support ticket that may be related to this, and the Support rep has requested some more information from you. Once Support receives those details, they should be able to advise you on your configuration and help troubleshoot. If you gain some insights that may be helpful to others in the process, please share those here. Thanks!

3

Hi Kate, the support case is unrelated to this post.

4

Hi @rhysgottwald,

With the most recent release we've added a flow step debugger. If the errors are occuring on the import step, you can turn on the debugger for that flow step to troubleshoot the errors you are receiving. If you are receiving 51 errors, it is likely that many of them (if not all) are being caused by a single misconfiguration. If you are still unable to identify the cause of your errors, please open a support ticket or attend an office hours session.

See Intro to Error Management 2.0 for more information on the latest tools available in the software to troubleshoot errors.

Tom

5

I am not sure if the following solution is any better than viewing the retry data in the UI, but you can always download all the errors to a CSV file. There is a download button top right. See following pic.

5301043caa20740200000001-3b7529f5139b4d57821de6a9a99bd2cf.png
5301043caa20740200000001-3b7529f5139b4d57821de6a9a99bd2cf.png2560×596 145 KB

In the CSV file, there is a column called 'traceKey', and the values in this column might help you find the original line in your source file. If the values in this column are not helpful as-is, then you could change what gets outputted here via a field in the data loader source bubble advanced section. See pic below. You could set this field to {{{my_line_num}}}, and then just use excel or equivalent to calc/output the line number values in this column before uploading the CSV file to integrator.io, etc... Hope this helps.

5301043caa20740200000001-f66903cb53cd43b5bf7632211bd9f175.png
5301043caa20740200000001-f66903cb53cd43b5bf7632211bd9f175.png1444×776 37.5 KB

6

@tomsantiago thanx for the feedback, but this is not a flow misconfiguration, it is a problem with the data. This is to import the take on data for go live and the reasons for the error is incomplete data.

@scotthenderson Your solutions seems to be what I am after, I will give it a try now and let you know

7

@scotthenderson your solution is exactly what I am after. THANX!

But this has given rise to another issue. If I do not group the data I see it as follows

{
  "record": {
    "External ID": "100035",
    "Line Id": "1",
    "Line External ID": "100035_1"
  }
}

and this works

{{{record.[Line External ID]}}}

But when I group it by External ID I see the data as this 

{
  "rows": [
    {
      "External ID": "100035",
      "Line Id": "1",
      "Line External ID": "100035_1"
    }
  ]
}

and now I cannot find the syntax to access Line External ID
I have tried the obvious ones like

{{{record.rows.[Line External ID]}}}
{{{rows.[Line External ID]}}}

And a few others but it retunes null..

So how do I access the field now?

I have tried.

8

Here is how to get to the values in the first row when you are doing grouping.

{{{rows[0].[External ID]}}} or {{{rows.0.[External ID]}}}

More background info: after grouping rows together via a key column in a CSV file, we change the handlebars context variable 'record: {}' to 'rows: []' in all the AFE 2.0 models/UI so that it is more obvious how to work with the different data structure.

9

Thanx @scotthenderson I assume then that the array index value will change automatically as the import runs?

10

I have tried both these and they work in the editor but not when I run the import.

11

rows[0] will always be the first row in the record that is currently being processed. Saying this another way, if you are grouping rows together via a key column in a CSV file, then integrator.io will do the groupings first, and then the AFE handlebars expressions will be given just a single record/grouping, and then behind the scenes integrator.io will iterate through all the records/groupings one by one, and run the expression on each individual record/grouping, etc...

I am not sure why it is not working when you run the actual import, and for this I would contact support to show them in a quick meeting. Hopefully it is a quick fix.