In this article we compiled issues and solutions when trying to connect on NetSuite. You might face role, users, or access tokens issues.
When troubleshooting a connection issue, the first step is to check if you're properly connected with the correct role ('Spendesk native integration'). Frequently, the selection of Choose role is neglected on the connection screen.
For context, when you install our bundle during the connection process, NetSuite creates a new role. A role is a defined access configuration which include sets of permissions for viewing and editing data. The role we need is called 'Spendesk native integration". It assigns all required permissions to it so that Spendesk can upload data on NetSuite. Additionally, NetSuite makes standard transaction forms preferred for this role (more on forms here). Finally, we ask you to attach this role to a NetSuite user.
The easiest way to check how Spendesk was connected to NetSuite is by looking at access tokens (Setup > Users/Roles > Access Tokens).
Important note:
An authentication token (security token) is a “trusted device” used to access NetSuite. It can be seen as an electronic key that enables a user to authenticate and prove his identity by storing some sort of personal information.
The "Application" column contains the name of the Integration that was created during the connection process. Therefore, the lines that have something to do with 'Spendesk' in the Application column are the ones we are interested in. As new access token is created every time you connect Spendesk to NetSuite, there should be as many 'Spendesk' lines as there are connections (from the Spendesk entity to the NetSuite subsidiary).
Checking the User and Role columns can help you determine two things:
Whether the correct role was chosen when connecting.
Whether the role was attached to the correct user.
If you see that the role is not 'Spendesk native integration' (e.g. Administrator or Accountant) or that the user is not the one performing exports, then they need to disconnect in Spendesk and reconnect again.
Important note:
Notice that there is usually a very limited number of tokens that can exist at the same time, so it's always a good idea to clean them up. Unused access tokens can be revoked by going to Edit > Revoke.
You can also check your SOAP Web Services and Token based authentication toggles. Sometimes these two settings are not configured and it causes issue when trying to connect. You can check that they are enabled under under Setup > Company > Enable Features, on the SuiteCloud tab. In such case the connection cannot be established between Spendesk and NetSuite despite doing everything else properly.