Ability to pinpoint which record failed in the view errors listAnswered
Suggested by Alex Placito
"You can currently see all data being sent, but if it fails on a particular record, you can't tell which one is the culprit. You have to do some sleuthing, scanning through JSON retry data and moving back and forth between integrator.io and NetSuite, checking departments and accounts in NetSuite to see which ones don't exist"
Could you please expand on your scenario? When a record flows through the integration and it fails in a specific flow step, the flow dashboard will show the step that fails and the record (by viewing its retry data).
I think when I was mentioning this to Courtney, I was actually referring to line items / sublists within NetSuite on a transaction.
For example, if I'm importing a Journal Entry with potentially hundreds of line items, and my mapping contains a lookup for the GL account on the JE line, when the record import fails, I don't know which line it failed on. This may actually be more of a NetSuite limitation, now that I think about it.
However, if it's at all possible for Celigo to identify which line item generated an error, that would be helpful.0
When importing journal entry line items and the import fails, NetSuite does not tell which line item it failed on. Hence, the platform cannot identify which line items fail either. This validation or check can be carried out inside a script to validate specific business rules that apply to your situation. Here is KB link for adding scripts to your flow.0
Please sign in to leave a comment.