NetSuite Changes: Then and Now
A new feature that came out of the NetSuite 2019.1 Release was account-specific domains in the NetSuite UI. This feature provides easier access to multiple accounts simultaneously.
An account-specific domain is a domain that is unique to your account because it includes your account ID in the URL. NetSuite has already implemented the account-specific domains in the UI feature in sandbox accounts and is now doing the same for Commerce accounts too.
What Changed / is Changing?
Back in March of 2019, NetSuite activated an account-specific domain in your production account. The same will soon (June 2020) be occurring for standard NetSuite commerce shopping and checkout web stores. Custom domains are not impacted.
What Users Can Expect
Important Note: You do not need to take any action for this change to the domain formats.
There is no change in the way users will access the production account. Users will access the account in the usual way, by logging in to NetSuite at https://system.netsuite.com. In the past, when users log in to your NetSuite production account, the URL in the browser looked something like this:
In March of 2019, account-specific domains were activated in your production account. You may have noticed that the URL in the browser changed, as shown in this example (where the account ID is 123456):
As an example, here is the screen shot of the company specific URLs found under company information. The below case is for SB2 of account 4148527:
New Commerce Domain Changes
For the new Commerce domain changes effective in June 2020, they will change from:
to https:// 123456.shop.netsuite.com/
from https:// checkout.netsuite.com/?c=123456
to https:// 123456.secure.netsuite.com/
You may need to update your company’s firewall to allow access from your account-specific domain. See Firewall Configuration below.
Several NetSuite help topics suggest adding “*.netsuite.com” to your firewall configuration. This is not always possible. If the firewall in your company’s infrastructure abides by strict rules, it will not accept URLs that include an asterisk (*) as a wildcard character. If this is the case for your company, you must add your account-specific domains to the firewall configuration.
To update your company firewall to accommodate your account-specific domain:
An example of the new account-specific domains for the UI that you must add to your firewall is like the following, where the <accountId> represents a variable that you must replace with the account ID of your production account:
|Add to your firewall:||For example, if your production account ID was 123456, you would add this to your firewall:|
Benefits of an Account-Specific Domain in the UI
When both your production and your sandbox accounts have account-specific domains, it will be easier to access both accounts at the same time, in separate tabs in the same browser. See the following procedure.
To access your production and sandbox account at the same time:
After this change, you will be able to access both your production account and your sandbox simultaneously. The method for doing so is slightly different than the method currently documented in the Help Center.
- Open your browser and log in to your NetSuite production account.
- Select a role in your sandbox account, but right-click and specify “Open in a different tab”.
- Click the tab with your production account role.
- Click Login and log in to NetSuite again.
Now, you have active sessions in both your production and your sandbox account. If you have multiple sandbox accounts, and the account-specific domain is active in all your accounts, you can use the procedure with any sandbox in which has an account-specific domain.
If you require assistance or more information, please contact Keystone.
Keystone. Your Chicago area on-demand software solution and integration provider.
Call – 866-546-7227 | Email – firstname.lastname@example.org