Missing mapped fields while import sales order to NetSuite

Integrator.io
, ,
1

Does anyone experiencing the same issue here?

Our integration is up and running for a while(at least a year), but recently some fields is missing in the sales order.

A very important fields call order/po#(extreference) is used for identify duplicate orders, but is also missing too :s

2

@johnsonlin,

It looks like you're working with our Support team on this, which is great since they can look into your specific configuration and assist. If there are any insights that come from that process that could be beneficial to others in the Community, we appreciate you sharing here when it's resolved. Thanks!

Tom

3

I recommend contacting customer support for help. Support will likely do the following steps, and you can do the same if you are familiar with these things.

  1. Check the audit log for the flow to see if anything changed.
  2. Check the mapping on the NetSuite import to make sure the missing fields are being mapped correctly.
  3. Check NetSuite to make sure the missing fields are settable in the UI on the same form and NetSuite role that the flow is using.
  4. Enable debug logs for the NetSuite connection, and then run the flow again, and then check to see if values for the missing fields are being sent to NetSuite.
  5. If the missing fields use a lookup to find a value, then perhaps the settings on the lookup are not accurate, or perhaps duplicates made it into NetSuite somehow, and now integrator.io cannot find a unique match, etc...
  6. Maybe there is something in NetSuite that has changed like the role or form permissions being used by the flow, or perhaps some other setting in NetSuite was changed affecting this.
4

Hi Soctt,

Actually I've manually everything on the list.

1. This happen from 4/13, but no one touch integration after Feb.

2. All mapping is correct.

3. I've check debug and the script looks correct, I saw `nalpisetvalue('refnum', xxxxxx). but in NS this field is empty.

4. Role is admin.

I'm still waiting on support reply on this ;s

5

Regarding #3 and #4, very interesting, and you should consider opening a NetSuite support ticket in parallel and let NetSuite know you are using a SuiteScript to set this field using an Admin role and it is not sticking.

6

I'm having this same issue, did you ever find resolve for this @johnsonlin?

UPDATE:

Figured this out. It was due to the field being updated to NOT store value. Store value should be checked for custom netsuite fields