Troubleshooting Other Integration Issues

Note:

This help topic is a placeholder. Content will be added gradually to these pages. For information about troubleshooting the integration, see NetSuite Integration.

Please review the Help Center Updates regularly for a summary of changes made to NetSuite Integration help topics.

Scenario	Possible Solutions
After configuring the integration, when trying to run the integration or synchronize NetSuite custom fields in SuiteProjects Pro, an "Invalid login attempt" error message appears.	The problem most likely relates to token-based authentication (TBA). If the Enable Direct TBA box is checked on the NetSuite Connector administration form in SuiteProjects Pro, verify that the user access token was generated for the `Internal NS Application OPENAIR` integration application. Verify the User Token ID and User Token Secret. If you made a note of the user token ID and secret in a safe place, make sure that you do not include any leading or trailing white space characters (space, tab, line feed, carriage return) with the user token ID and secret. It is often the case that additional white spaces characters before or after the user token ID or secret are copied if you triple-click to select the entire paragraph in a word-processing or other application, for example. You can generate a new user token ID or secret at any time. To generate a new user token ID or secret, revoke the existing token and create a new one in NetSuite. After you generate the new user token ID or secret, enter these credentials in SuiteProjects Pro. For more information about generating TBA access tokens for the integration, see Creating and Assigning an Access Token for the Integration. See also Enabling the SuiteProjects Pro Integration in NetSuite. For more information about entering TBA access token credentials in SuiteProjects Pro, see Connecting SuiteProjects Pro to NetSuite for the Integration.
NetSuite records of a certain type are not imported into SuiteProjects Pro using real-time record import.	Ensure that integration script deployments for that record type are deployed for all roles and executed as the `SuiteProjects Pro Integration Administrator` or as the custom role you created for the integration. See Verifying Integration Script Deployment Settings. For example, if you want to import purchase orders, vendor bills, or vendor credits from NetSuite into SuiteProjects Pro, the following scripts must be deployed for or all roles and executed as the `SuiteProjects Pro Integration Administrator` or as the custom role you created for the integration: `SuiteProjects Pro: PO/VB/VC Validate` or `SuiteProjects Pro: PO/VB/VC Validate 2.1` `SuiteProjects Pro: PO/VB/VC Save` or `SuiteProjects Pro: PO/VB/VC Save 2.1` `SuiteProjects Pro: Send to SPP` or `SuiteProjects Pro: Send to SPP 2.0` Important: Either the SuiteScript 1 or the SuiteScript 2 version of each script must be deployed, but not both. Ensure that the user event script sending the record to SuiteProjects Pro runs after all other user event scripts for the record type. See Verifying User Event Scripts Running Order
The NetSuite integration logs show this error for all new and already integrated records of a certain type: `ERROR: The currency "" for NetSuite <record type> "<name>" has not been defined in SuiteProjects Pro.`	Verify that the Multiple Currencies feature is enabled in your NetSuite account. See Enabling the Multiple Currencies Feature (External link to NetSuite SuiteAnswers - Answer ID: 7714). Verify that the `SuiteProjects Pro Integration Administrator` role or custom role you created for the integration includes `Full` access permission for `Currency` (Lists subtab). See NetSuite Permissions Required for the Integration. If there is only the root subsidiary in your NetSuite account, create another subsidiary. See Creating Subsidiary records (External link to NetSuite SuiteAnswers - Answer ID: 7714). Ensure NetSuite subsidiary information is mapped to a SuiteProjects Pro hierarchy. See Map NetSuite employee subsidiary to employee hierarchy, Map NetSuite customer subsidiary to customer hierarchy, and Map NetSuite project subsidiary to project hierarchy. Run a full synchronization and include the import workflow for the NetSuite record type. Go to Setup > Integration > SOAP Web Services Preferences. Check the Run server SuiteScript and trigger workflows box. Click Save. See Enabling the SuiteProjects Pro Integration in NetSuite. Note: This SOAP web services preference, when disabled, prevents the SuiteScript that is used to fetch the integration preferences set in the NetSuite account from running. The NetSuite integration does not handle the currency for the NetSuite record correctly because it expects the NetSuite account to use a single base currency account when in fact it uses multiple base currencies.

Scenario

Possible Solutions

After configuring the integration, when trying to run the integration or synchronize NetSuite custom fields in SuiteProjects Pro, an "Invalid login attempt" error message appears.

The problem most likely relates to token-based authentication (TBA).

If the Enable Direct TBA box is checked on the NetSuite Connector administration form in SuiteProjects Pro, verify that the user access token was generated for the Internal NS Application OPENAIR integration application.
Verify the User Token ID and User Token Secret. If you made a note of the user token ID and secret in a safe place, make sure that you do not include any leading or trailing white space characters (space, tab, line feed, carriage return) with the user token ID and secret. It is often the case that additional white spaces characters before or after the user token ID or secret are copied if you triple-click to select the entire paragraph in a word-processing or other application, for example.
You can generate a new user token ID or secret at any time. To generate a new user token ID or secret, revoke the existing token and create a new one in NetSuite. After you generate the new user token ID or secret, enter these credentials in SuiteProjects Pro.

For more information about generating TBA access tokens for the integration, see Creating and Assigning an Access Token for the Integration. See also Enabling the SuiteProjects Pro Integration in NetSuite.

For more information about entering TBA access token credentials in SuiteProjects Pro, see Connecting SuiteProjects Pro to NetSuite for the Integration.

NetSuite records of a certain type are not imported into SuiteProjects Pro using real-time record import.

Ensure that integration script deployments for that record type are deployed for all roles and executed as the SuiteProjects Pro Integration Administrator or as the custom role you created for the integration. See Verifying Integration Script Deployment Settings.

For example, if you want to import purchase orders, vendor bills, or vendor credits from NetSuite into SuiteProjects Pro, the following scripts must be deployed for or all roles and executed as the SuiteProjects Pro Integration Administrator or as the custom role you created for the integration:
- SuiteProjects Pro: PO/VB/VC Validate or SuiteProjects Pro: PO/VB/VC Validate 2.1
- SuiteProjects Pro: PO/VB/VC Save or SuiteProjects Pro: PO/VB/VC Save 2.1
- SuiteProjects Pro: Send to SPP or SuiteProjects Pro: Send to SPP 2.0
Important:
Either the SuiteScript 1 or the SuiteScript 2 version of each script must be deployed, but not both.
Ensure that the user event script sending the record to SuiteProjects Pro runs after all other user event scripts for the record type. See Verifying User Event Scripts Running Order

The NetSuite integration logs show this error for all new and already integrated records of a certain type:

ERROR: The currency "" for NetSuite <record type> "<name>" has not been defined in SuiteProjects Pro.

Verify that the Multiple Currencies feature is enabled in your NetSuite account. See Enabling the Multiple Currencies Feature (External link to NetSuite SuiteAnswers - Answer ID: 7714).
Verify that the SuiteProjects Pro Integration Administrator role or custom role you created for the integration includes Full access permission for Currency (Lists subtab). See NetSuite Permissions Required for the Integration.
If there is only the root subsidiary in your NetSuite account, create another subsidiary. See Creating Subsidiary records (External link to NetSuite SuiteAnswers - Answer ID: 7714).
Ensure NetSuite subsidiary information is mapped to a SuiteProjects Pro hierarchy. See Map NetSuite employee subsidiary to employee hierarchy, Map NetSuite customer subsidiary to customer hierarchy, and Map NetSuite project subsidiary to project hierarchy.
Run a full synchronization and include the import workflow for the NetSuite record type.
Go to Setup > Integration > SOAP Web Services Preferences. Check the Run server SuiteScript and trigger workflows box. Click Save. See Enabling the SuiteProjects Pro Integration in NetSuite.

Note:
This SOAP web services preference, when disabled, prevents the SuiteScript that is used to fetch the integration preferences set in the NetSuite account from running. The NetSuite integration does not handle the currency for the NetSuite record correctly because it expects the NetSuite account to use a single base currency account when in fact it uses multiple base currencies.