Skip to main content

Updating your NetSuite role for Blue Onion

J
Written by Jessie Carlile

Please complete these changes by December 31, 2026, ahead of NetSuite’s 2027.1 update.

Blue Onion is moving its NetSuite sync to NetSuite’s newer REST and SuiteQL APIs, as NetSuite phases out its SOAP API, and will also offer OAuth 2.0 as a connection option. To keep your data flowing, a NetSuite administrator needs to update the role Blue Onion uses, which takes about 15 minutes.

1. Turn on the required features

Go to Setup > Company > Enable Features. Then, click the SuiteCloud tab.

In the SuiteTalk (Web Services) section, checkmark: SOAP Web Services and REST Web Services.

In the Manage Authentication section, checkmark: Token-Based Authentication and OAuth 2.0.

In the SuiteScript section, checkmark: Server SuiteScript.

Click Save.

2. Open the Blue Onion role

  1. Go to Setup > Users/Roles > Manage Roles > Search. Search for “BlueOnion” or “Blue Onion”.
    ​

  2. Once you find the role, click “Edit”.
    ​

3. Give the role access to every subsidiary

On the role's main page, under Subsidiary Restrictions, select All. Then, scroll down to the Permissions section, and proceed with Step 4.


​

4. Check the permissions of the role

On the Permissions tab, make sure every permission below is present at the level shown, and add any that are missing. Don’t remove or lower any permissions the role already has, even ones not listed here.
​

Transactions (all View)

  • Find Transaction

  • Sales Order

  • Invoice

  • Credit Memo

  • Customer Payment

  • Customer Deposit

  • Customer Refund

  • Cash Sale

  • Cash Sale Refund

Additionally, if using Blue Onion to post journal entries, deposits or cash sales to your NetSuite:

  • Make Journal Entry (set to Full)

  • Deposit (set to Full)

  • Cash Sale (set to Full)
    ​

Reports

  • SuiteAnalytics Workbook (View) *Edit may be the only option that appears

Lists (all View)

  • Accounts

  • Classes

  • Currency

  • Customers

  • Departments

  • Documents and Files

  • Items

  • Locations

  • Perform Search

  • Subsidiaries

  • Vendors

Setup

  • REST Web Services (Full)

  • SOAP Web Services (Full)

  • Log in using Access Tokens (Full)

  • Log in using OAuth 2.0 Access Tokens (Full)

  • Accounting Lists (View)

  • Custom Body Fields (View)

  • Custom Column Fields (View)

  • Custom Fields (View)

  • Custom Lists (View)

  • Custom Record Types (View)

  • Custom Segments (View)

  • Deleted Records (View)

  • Manage Accounting Periods (View)

  • SuiteScript (View)

Custom Record

  • Keep this section as-is

Click Save.
​
​

5. Give the role access to your custom segments

If you use custom segments with Blue Onion: go to Customization > Lists, Records & Fields > Custom Segments. For each applicable segment, open it, go to the Permissions subtab, add the Blue Onion role with View, and save.

FAQs

1. Which NetSuite role and integration record does Blue Onion use?

Good question! The role and integration record live inside your NetSuite account, so they aren’t visible on our end. If you don’t know which role it is, try searching for the role in Netsuite. Go to Setup > Users/Roles > Manage Roles > search, then search for “BlueOnion” or “Blue Onion”, since the person who set up your role may have labeled it with our name. If you have trouble finding the role, just let us know.
​

2. Will we keep using token-based authentication, or will we need new OAuth 2.0 credentials?

NetSuite is retiring token-based authentication, so once our REST integration is ready, you’ll reconnect using OAuth 2.0.
​

3. After we enable REST, who makes the switch, and when? Does the test step in production only read data, or does it create records?

We’re aiming to have REST ready by the end of Q4 2026. From what we know so far, the switch happens when you connect through OAuth 2.0, so there’s no separate cutover for you to manage. The test step is read-only, so it won’t create or change any records.
​

4. Will our external IDs and upsert logic stay the same?

Yes. Everything stays the same, so you won’t see duplicate records.
​

5. If something goes wrong, can we switch back to SOAP?

Unfortunately not. Starting with NetSuite’s 2027.1 release, NetSuite will no longer support token-based authentication, which SOAP depends on. Once you’ve moved to REST, switching back isn’t an option. If anything comes up after the move, our team will be right there to help you sort it out.
​

6. When do I need to make these changes by?

Please complete these changes by December 31, 2026, ahead of NetSuite’s 2027.1 update.

Did this answer your question?