NetSuite has deprecated the "Full Access" role that is used in the Kantata OX integration. To maintain the integration between NetSuite and Kantata OX, changes need to be made in both NetSuite and the M-Bridge integration platform.
Perform the following in NetSuite, in order:
- Make sure the Mavenlink Token Bundle is installed in NetSuite.
- Confirm required feature settings in NetSuite.
- Confirm required permissions for the Mavenlink Integration Custom Role.
- Migrate to the Mavenlink Integration Custom Role.
- Create a new Access Token.
- Retrieve the Account ID.
Then perform the following in M-Bridge, in order:
- Create a new service in M-Bridge with the new Access Token.
- Create new mappings in M-Bridge.
- Update Scenarios with new mappings in M-Bridge.
This article outlines the exact steps to take in NetSuite, and then links you to the steps to take in M-Bridge.
Install the Mavenlink Token Bundle
Make sure the Mavenlink Token Bundle is installed in the NetSuite environment you would like to integrate with. If it is not already installed, perform the following steps to install the bundle.
- In NetSuite, navigate to Customization > SuiteBundler > Search & Install Bundles.
- In the search bar, search for
Mavenlinkand select Mavenlink Integrations Token Based Auth. The Bundle Details page displays.
- Click Install on the top left of the Bundle Details page. This will take you to the Preview Bundle Install page.
- Click Install Bundle on the top left of the Preview Bundle Install page to begin the installation. This may take a few minutes. The Mavenlink Integrations Token Based Auth bundle is installed now.
Certain features and settings need to be enabled in the NetSuite environment for the integration with Kantata OX to function correctly.
This section outlines how to confirm the settings.
- Navigate to Setup > Company > Enable Features.
- Ensure that these features are enabled under each subtab:
- Project Management
- (optional) Intercompany Time and Expense (enable if resources will be assigned to projects outside of their home subsidiary in NetSuite)
- Expense Reports
- Time Tracking
- Weekly Timesheets
- Time Tracking for CRM
- Client SuiteScript
- Server SuiteScript
- Soap Web Services
- Token-Based Authentication
- Override Rates on Time Records
- Navigate to Setup > Users & Roles > Manage Roles.
- Find the Mavenlink Integration Custom Role, and click Edit.
- Under the Subsidiary Restrictions banner, select ALL. This makes all subsidiaries accessible to the Mavenlink Integration Custom Role.
- Navigate to the following Permissions subtabs, and confirm the following permissions with Full level access:
- Permissions > Transactions
- Expense Report
- Track Time
- Permissions > Lists
- Employee Record
- Expense Categories
- Project Tasks
- Projects (or "Jobs")
- Permissions > Setup
- Access Token Management
- Accounting Lists
- Allow JS / HTML Uploads
- Log in using Access Tokens
- User Access Tokens
- Web Services
- Custom Fields
- Permissions > Transactions
- Click Save.
What is a Role in NetSuite?
A role is a customizable set of permissions that can be assigned to employees in NetSuite. An employee assigned with the Mavenlink Integration Custom Role will display as the creator and updater of records that the integration writes to in NetSuite.
If an employee profile in NetSuite dedicated to integrations exists, we recommend adding the Mavenlink Integration Custom Role to that profile. If there is not yet an employee profile dedicated to integrations in NetSuite, we highly recommend creating one. This makes data and user management easier and cleaner.
Alternatively, the Mavenlink Integration Custom Role can be assigned to any existing user with access to NetSuite.
How to Assign the Mavenlink Integration Custom Role
- In the top search bar, type the name of the user you want to assign the Mavenlink Integration Custom Role to. As you start typing the name, the drop-down will populate with a list of relevant records.
- Select the
Employee: <name>record. The Employee record displays.
- Click Edit.
- Navigate to the Access subtab. If the employee doesn’t have access to NetSuite, check the Give Access box. You can also send the employee a welcome email or manually set a password for them here.
- Under the Roles subtab, add the Mavenlink Integration Custom Role.
- Click Save.
- Navigate to Setup > Users/Roles > Access Tokens > New.
- The Access Token page displays. Select the following:
- Under the Application Name field, select Mavenlink Token Based Integration.
- From the User drop-down, select the NetSuite employee profile that the Mavenlink Integration Custom Role was added to.
- From the Role drop-down, choose the Mavenlink Integration Custom Role.
- The Token Name field is auto-populated by the Application Name, User, and Role, but you can rename it.
- Click Save. The Access Token page reloads with the Token ID and Token Secret information.
- Copy and save the Token ID and Token Secret.
Note: This is the only time this information is displayed. Once you navigate away from this page, the Token ID and Token Secret are no longer visible. If you do not save or if you lose the Token ID and Token Secret, you will have to generate a new Access Token.
- Navigate to Setup > Company > Company Information, and locate the Account ID for the NetSuite environment being integrated.
- Copy and save it to the same place with your Token ID and Token Secret.
Note: Each NetSuite environment has a unique Account ID. A sandbox account and a production account will have different Account IDs.
New M-Bridge services and mappings need to be created for new NetSuite environments, and scenarios need to be updated. Perform the following steps in order:
We recommend giving a name to your Service that indicates which NetSuite environment it is for.
New Mappings (users, job status, etc.) need to be created in M-Bridge for each NetSuite environment because the internal IDs of mapped objects are different in every environment.
As with Services, we recommend giving names to your Mappings that indicate which NetSuite environment they are for.
Once new mappings have been created, make sure you update each scenario to use the new mappings.