Troubleshooting Errors in the Salesforce - NetSuite Integration App

[INSUFFICIENT_PERMISSION]

[INSUFFICIENT_PERMISSION]

The user role which is trying to create or update a record in either Salesforce or NetSuite does not have sufficient permissions to make that change.

1. Identify the user role for that system from the Connections tab in the Integrator dashboard.
2. Check whether that user role has sufficient permissions to create and update relevant records in either Salesforce or NetSuite (as appropriate).
3. If the required permissions are missing, then grant them to this role.
4. Retry the data flow.

[INVALID_KEY_OR_REF] [ Invalid company reference key XXXX]

[INVALID_KEY_OR_REF] [ Invalid company reference key XXXX]

During Opportunity Sync, if the account in Salesforce is already 'inactive' in NetSuite, the Integration App will no longer be able to locate the record from the Customers List. The error will then be returned providing the Internal ID of the customer record in NetSuite to easily locate which record is being looked for.

1. Go to the list of Customers in NetSuite and look for the company with the Internal ID provided on the error.
   
   Note: Make sure that the list shows 'Inactive' records (checkbox to show the Inactive records is available below the page)
2. Make the record Active again by unchecking the 'Inactive' checkbox under the 'System Information' tab of the customer record in NetSuite.
3. Save.

[INVALID_KEY_OR_REF] [Invalid salesrep reference key XXX.]

[INVALID_KEY_OR_REF] [Invalid salesrep reference key Employee_Internal_Id.]

This error appears if the employee that is being set as the sales rep is not a valid option in NetSuite.  In this error message, Employee_Internal_Id will be the internal id of the employee record in NetSuite that is being set into the sales rep field.

1. Go to the employee record in NetSuite with the internal id Employee_Internal_Id.
2. Make sure the employee record is active (the 'Inactive' field is not checked).
3. On the Human Resources tab, make sure the 'Sales Rep' field is checked.
4. Verify that you can select the employee in the 'Sales Rep' field on a Quote or Sales Order in NetSuite.
5. If you have multiple subsidiaries enabled, make sure the integration user's role (Setup -> Manage Roles) has access to the subsidiary that the employee belongs to.
   1. By default, Celigo integrations use the Celigo Integration Admin role.

[CONTACT_ALREADY_EXISTS]

 [CONTACT_ALREADY_EXISTS]

If the Account in Salesforce has two or more Contacts with the same First Name and Last Name then this error will appear. While Salesforce allows two Contacts with the same first name, last name, NetSuite does not allow two Contacts for the same Customer to have the same first name and last name.

Update the name of one of the Contacts in Salesforce and try the sync again

INVALID_LOGIN

INVALID_LOGIN

This error will appear if the credentials for either Salesforce or NetSuite are not correct.

Check the Connections tab in Integrator and update the credentials for NetSuite or Salesforce as appropriate.

INVALID PRICE REFERENCE KEY -1 FOR ITEM <NULL>

[INVALID PRICE REFERENCE KEY -1 FOR ITEM <NULL>]

If the Salesforce Product and NetSuite Item are not in sync, this error will show.

SF Product and NS Item are not in sync. ID mapping is not there

There are two options to resolve this:

1. Turn on the NetSuite Item to Salesforce Product flow in the Integrator dashboard. Edit the Item in NetSuite and then click Save. This Item will get synchronized with Salesforce Product.
2. You can also manually map the Salesforce Product with NetSuite Item by adding the Internal ID of the NetSuite Item in the Salesforce Product and vice – versa.

RCRD_DSNT_EXIST

"RCRD_DSNT_EXIST: That record does not exist." error message is getting displayed.

This error will appear if the Integration App cannot find the appropriate record in NetSuite while syncing from Salesforce. This error typically appears when there is a lookup failure from Salesforce to NetSuite.

Lookup failed. SF to NS

Check the NetSuite account and make sure that the relevant record is present in NetSuite.

UNIQUE_CUST_ID_REQD

UNIQUE_CUST_ID_REQD: A customer record with this ID already exists. You must enter a unique customer ID for each record you create. To correct this record, click <a href='javascript:history.go(-1);';>back</a> and enter a new customer ID in the Customer field. Then, click Submit.

By default, NetSuite does not allow two Customers with the same name. If there are two Accounts in Salesforce with the same name then this error will appear when the Integration App tries to sync them to NetSuite as Customers.

There are two options to resolve this:

1. Turn on auto-numbering of records in the NetSuite Account.
2. Update the name of one of the Accounts in Salesforce.

401

error response from endpoint 401 – { error code – "Could not determine Customer Compid"}

If the credentials used by the Integration App to connect to Salesforce are invalid and the user is trying to sync an Opportunity with an EchoSign document attached.

Check the Connections tab in Integrator and update the credentials for NetSuite or Salesforce as appropriate.

INVALID_KEY_OR_REF

INVALID_KEY_OR_REF: Invalid item reference key 1334 for subsidiary 1.

In NetSuite OneWorld, when a Sales Order is created, the Customer and Items in the Sales Order should be in the same subsidiary.

This error will appear if you sync an Opportunity from Salesforce to NetSuite where the Account (Customer in NetSuite) and Product (Item in NetSuite) are not in the same subsidiary in NetSuite.

Make sure Customer and Item are in the same subsidiary in NetSuite.