Oracle Netsuite authentication

UiPath Integration Service supports NetSuite token-based authentication with a custom authentication type. For additional information, see the NetSuite official documentation: Token-Based Authentication.

Note:

To use token-based authentication, you must set up a new user linked to a single role. An existing user may have multiple roles, and the role used by the web service might not match the role selected as the web services role.

Prerequisites

To authenticate using a token-based custom authentication, you must provide the following credentials:

• Consumer key
• Consumer secret
• Access token ID
• Access token secret
• Account ID

You also need to enable token-based authorization for your account, create an integration record for your application, create a relevant role, assign the role to a user, and generate your credentials/token.

To complete the setup required for creating a connection to NetSuite, take the following steps in your NetSuite account:

Enable token-based authorization for your account

1. Sign in to NetSuite, navigate to Setup > Company > Enable Features.
2. In the SuiteCloud tab, scroll down to the Manage Authentication section.
3. Enable Token-Based Authentication and select Save.

Create an integration record for your application

1. Go to Setup and select Integration > Manage Integrations > New to create an integration.
2. Provide a Name for your integration.
3. In the Authentication section:
   1. Enable Token-Based Authentication and TBA: Issue token Endpoint.
   2. Disable TBA: Authorization Flow and Authorization Code Grant.
   3. Enable User Credentials.
4. Select Save.
   
   

   

   
   
5. After saving your integration, your consumer key and secret are displayed. This is the only time that you can retrieve these values.
   
   

   

   
   

Create and assign user roles

1. Navigate to Setup > Users/Roles > Manage Roles > New to create a new custom role for the token-based authentication user.
2. On the Role page, take the following steps:
   1. Provide a Name for the role.
   2. In the Setup tab of the Permissions section, add the User Access Tokens & SOAP Web Services permission. Also add any additional relevant permissions based on your integration's needs and scope. For detailed information about available permissions, see Netsuite's documentation.
   1. Select Save.
      
      

      

      
      

      
      

      

      
      
3. After successfully creating the role, navigate to Lists > Employees > Employees. Either select an existing employee listing, or create a new one.
4. In the Access > Roles section of the Employee page, assign the role you created above. Select it from the Role menu and select Add. Click Save after assigning the role.

Generate the token

1. Navigate to Setup > Users/Roles > Access Tokens > New.
2. On the Access Token page, select the application, user, and role you created in the previous steps. Add a name for your token, and then select Save.
3. Your token ID and secret are displayed. This is the only time the token ID and secret are displayed.
   
   

   

   
   

Retrieve the account ID

1. From the Setup page, go to Company.
2. Under Company Information, select Account ID. You can also find the Account ID in the URL. For example, if the URL is https://12345_XYZ.app.netsuite.com/, your account ID is 12345_XYZ.

Enable Show Internal IDs

Follow the steps described in the NetSuite documentation to enable the Show Internal IDs setting.

This setting allows you to see the internal IDs for all fields, records, lists, workflow actions, and custom forms in NetSuite. The internal ID of an object is a required input property in NetSuite activities.

Add the Oracle NetSuite connection

1. Select Integration Service from Automation Cloud^TM.
2. From the Connectors list, select Oracle NetSuite. You can also use the search bar to narrow down the connector.
3. Select Connect to Oracle NetSuite.
4. Enter the required credentials and select Connect.

Concurrency limitation

NetSuite’s concurrency limits allow you to allocate a portion of your account’s concurrent request limits to specific integrations. Each account has restrictions on the number of requests that can be made to the web services at any given time. For more information, see the NetSuite Concurrency Limits documentation.

By default, NetSuite Connector limits the concurrent sessions it uses to five. You can change this value in: Setup > Integration > Manage Integrations. Select an integration, select the Edit button and enter a new value for Concurrency limit.

Important: This limitation can cause some activity invocation calls to fail if another user is using the same credentials. We recommend you keep a separate set of credentials for your automation.