Skip to main content
CFCX Work

UI Updates in NetSuite 2020.2

2020.2 UI |

Critical Announcements in SuiteAnswers

As of 2020.2, critical announcements are displayed at the top of the page in SuiteAnswers.

Critical announcements deal mainly with performance issues or planned maintenances. Critical

announcements are displayed on every page until the user closes them by clicking X on the top right of the announcement. The announcement reappears only after the user logs out and logs back in to SuiteAnswers. Each type of critical announcement is displayed in a different color:

  • Maintenance announcements are purple.
  • Performance issues are red.
  • General announcements are orange.

Code Sample Highlighting

SuiteAnswers now has a new code sample highlighting feature that highlights lines or parts of the code

sample in all types of articles, which results in a better readability of the code samples. The code samples now also include a Copy button that you can use to copy the whole code sample onto your clipboard.

OpenAir users who open a link to a SuiteAnswers article without being logged in to OpenAir are now

redirected to the OpenAir login page. After users log in to OpenAir, a support page opens. Users can click Go to SuiteAnswers to be redirected to the SuiteAnswers article. Advance Notice – End of Support for Reset Buttons on

Standard Form Pages

As of 2021.1, NetSuite will no longer support the use of the Reset button on standard form pages. NetSuite will no longer address defects or issues related to Reset buttons on standard form pages. As a result of this deprecation, you will not be able to see a reset button on any form or record. To revert to the original version of the form or record, use the refresh function in your browser. For more information, see the help topic Using Buttons in NetSuite. You will still be able to access existing custom Reset buttons that you added using SuiteScript APIs.

Commerce Applications

Important: SuiteCommerce Advanced releases are available as unmanaged bundles. Accounts are not automatically upgraded to the latest version during the standard NetSuite phased release process. For existing implementations, taking advantage of enhancements in a given SuiteCommerce Advanced release requires you to migrate changes into your existing code base. For details, see the help topic Update SuiteCommerce Advanced. 2020.2.0 Release Notes The latest versions of SuiteCommerce, SuiteCommerce My Account, and SuiteCommerce Advanced SuiteCommerce, SuiteCommerce MyAccount, and SuiteCommerce Advanced.

  • Measuring Performance of Commerce Websites
  • Extension Manager Displays Automated Activations
  • Provide Translations in Custom Themes and Extensions
  • Enable Strike-Through Price Display for Configured Items
  • Hide the Add to Cart Button
  • Extensibility API Updates
  • Configuration Changes
  • Field Set Changes
  • Node.js Requirement Change
  • Third-Party Library Updates
  • Issue Fixes

Commerce Themes

Commerce Themes let you customize your site’s style and design. Complete release notes are available here: Commerce Themes Release Notes. Important: Commerce Themes are only available if they are provisioned and set up in your account. For more information, see the help topic Commerce Themes.

Commerce Extensions

Commerce Extensions provide additional functionality to your Commerce web store. Complete release notes are available here: Commerce Extensions Release Notes. Important: Commerce Extensions are only available if they are provisioned and set up in your account. For more information, see the help topic Commerce Extensions. Site Management Tools SMT Multi-Language Support for SMT Landing Pages and

Website Content

In NetSuite 2020.2, this lets you add your own translations to SMT Landing Pages and Website Content for your account. Language-specific domains let you create a domain for each language you want to include in your store. You can now use the SMT interface to add your translations instead of custom fields or a third-party solution. With the multi-language feature enabled, inside SMT there is also a domain switcher. The domain switcher lists all of your current multi-language enabled domains and lets you switch between them to preview without the need to leave SMT. For more information, see the help topic Multi-Language Sites.

SMT Enhanced Pages

In NetSuite 2020.2, you can now preview and manage enhanced pages from the Overview Pages list.

Enhanced pages will appear in the Pages list, as well as the Page Type filter after you make edits to

the enhanced page. Previously, you would log into SMT, navigate directly to the enhanced page, and preview and manage the content there. For more information about enhanced pages, see the help topic Enhanced Pages.

SMT Extensibility Enhancements

In NetSuite 2020.2, when creating a custom field type the List/Record and Multi-Select types now include the ability to add and remove items directly from the list in SMT. It also includes the ability to search the list directly in SMT. Also, longer lists are loaded in succession as the list is scrolled through. For more information, see the help topic Table of Custom Field Type Descriptions. And lastly, the CMS Page Types feature now supports child records. For more information, see the help topic CMS Page Types.

Commerce Platform

Commerce Platform includes platform capabilities that you can use to build and deploy a more interactive

Simplified Website Setup Form for SuiteCommerce InStore

The Web Site Setup form for SuiteCommerce InStore (SCIS) now contains only those fields that are specific to SCIS. This simplifies the process of setting up the website record. All fields formerly available on the form remain available to SuiteScript. Therefore, this change does not affect any existing scripts used with the Web Site Setup form. For more information, see the help topic Setting Up the SCIS Website.

Creation of Multiple Websites without Feature Enablement

Prior to 2020.2, you needed to enable the Multiple Web Sites feature before you could create multiple

websites. From 2020.2 onwards, all Commerce solutions customers have the ability to create multiple websites; there is no need to enable a feature to do this. However, you must have a website licence for each website. As the ability to create multiple websites is now available to all, the Multiple Web Sites feature has been removed from the Enable Features > Web Presence page.

For accounts with a single website, prior to 2020.2, going to Setup > Site Builder > Setup Web Site would

display the website record. From 2020.2 onwards, going to this location, shows the website name in the Web Sites list. Click Edit next to the website name to view the website record. When you create more websites, they are added to the list. For more information, see the help topic Multi-Site.

Account Specific Domains for Commerce Web Stores

Starting with NetSuite 2020.2, Commerce web stores must use account specific domains. Because of this change, there are new formats for standard NetSuite commerce shopping and checkout domains for your web store. These changes do not apply to custom domains. For affected customers using standard NetSuite domains, no action is required. These changes take place automatically, and users are redirected to your new domain. The new formats ensure that domains are account specific and do not refer to a specific data center. In addition, the “shopping” and “checkout” domain formats are now “shop” and “secure,” respectively. See the following comparison between the previous domain formats and account-specific domain formats. For example, if your NetSuite account ID was 123456 and pointed to the data center na1:

  • Your shopping domain could have previously looked like this: shopping.na1.netsuite.com/?c=123456. Now, your account-specific domain looks like this: 123456.shop.netsuite.com.
  • Your checkout domain could have previously looked like this: checkout.na1.netsuite.com/?c=123456. Now, your account-specific domain looks like this: 123456.secure.netsuite.com. For more information, see the help topics Domain Options for Web Stores and Set Up Domains for Web Stores.

Ability to Hide the Add to Cart Button in Web Stores

If you use Personalized Catalog Views on SuiteCommerce or SuiteCommerce Advanced 2020.2 or later, the Add to Cart button in your web store can be hidden for one or more customer segments. To configure the button’s visibility, use the Website Visibility Level options available in Customer Segments

Manager. There are two visibility options:

  • Display Fully - members of customer segments with this visibility level are able to see all items in the item segment and are able to add them to their shopping carts.
  • Disable Purchase - members of customer segments with this visibility level are able to see all items in the item segment but they cannot add them to their shopping carts. Note: If you have a SuiteCommerce Advanced website, the Disable Purchase option can be used only after you have upgraded to the 2020.2 release of SuiteCommerce Advanced or later. Do not use the Disable Purchase option if your site is using a SuiteCommerce Advanced release prior to 2020.2. A third visibility option, Hide Fully, is available only for the Unmapped Items item segment. This item segment contains all items that are not mapped to a customer segments. You can use the visibility options to define whether these items should be displayed to or hidden from all users. For more information, see the help topic Managing which Item Segments can be Viewed and Purchased.

Importing Static Groups Using CSV Import

NetSuite 2020.2 includes an enhancement to groups which allows you to import the following types of static group:

  • Contact
  • Customer
  • Employee
  • Partner
  • Project
  • Vendor With this enhancement, you can create new static groups or modify existing static groups using the Import Assistant. The Groups record type is available after the Relationships import type is selected in the Import Assistant. The following fields are available for import:
  • Entity Group
    • Comments
    • Email
    • Externalid
    • Group Type
    • Inactive
    • Internal ID
    • Name
    • Owner
    • Private
    • Restrict To
  • Entity Group Group Members
    • Name See the help topic CSV Imports Overview for details about how to import CSV files.

Data Center Agnostic NetSuite Checkout Subdomains

Starting with NetSuite 2020.2, NetSuite checkout subdomains are changing to allow you to make your subdomain data center agnostic. The NetSuite checkout subdomains affected by this change are:

  • securecheckout.com
  • onlinecheckout.com
  • webstorecheckout.com
  • suitecheckout.com With this change, the data center label of NetSuite checkout subdomains (for example: na0) is moved from the checkout URL component to the customizable domain prefix component. Because the subdomain is appended to the domain prefix, this does not affect the final checkout URL. This change happens automatically and does not affect your website. For optimal performance, we recommend that you then remove the data center label from the domain prefix and take steps to update links to your website. This means that your website would no longer be specific to one data center and would not be affected by future data center changes. You can see this change on the Domains tab of the Web Site Setup record. See the following example of what the fields look like before and after this change: Before: After: SuiteCommerce and SuiteCommerce Advanced Websites

SiteBuilder Websites

For SiteBuilder Sites, you can see an additional component has been added. While the datacenter label

has shifted to the domain prefix component, there is still a URL alias component that can be used to visit your website. For more information, see the help topic Link a Checkout Domain with your Web Store.

SuiteCommerce InStore

SuiteCommerce InStore (SCIS) uses a phased release process to distribute managed-bundle upgrades. Each phase consists of a different group of customers that receive the latest SCIS release. Administrators set up for customers within a phased group receive an email notification listing when their upgrade will occur.

  • Script Deployment Lists for Disabling by Context
  • Recovery for Issues when Tendering Cash, Check, or Custom Payments
  • Avoiding Storage Issues via a Fallback Catalog Limit
  • New Application Performance Management (APM) Sensors Note: Contact your account representative or Customer Support if you have questions about the availability of SCIS 2020.2.

Script Deployment Lists for Disabling by Context

If a script is not required under certain execution contexts, you can improve SCIS performance by disabling the script for those contexts. SCIS 2020.2 provides pre-configured searches to locate and edit the applicable scripts. The execution contexts that can be disabled are:

  • Web Application
  • Payment Postback You can safely disable scripts that run under these contexts. For more information, see the help topic Disabling a Script Deployment via its Context. Recovery for Issues when Tendering Cash, Check, or

Custom Payments

A cash, check, or custom payment might experience issues during the tendering phase, after tapping

Apply Payment. One type of issue is when a SCIS mobile device experiences a communications failure

while processing the payment. A different tendering issue is when the SCIS application is closed while a payment is tendering. SCIS now displays prompts with actions the sales associate can take to recover and complete a payment, such as reconnecting, resuming, going to Fallback, or dismissing the transaction. Applicable recovery options display in popup window, either when the issue occurs or when the SCIS application is restarted. For more information, see the help topic Recovering From Cash, Check, or Custom Tendering Issues.

Avoiding Storage Issues via a Fallback Catalog Limit

Mobile iOS and Windows devices have limits on the storage available for a Fallback catalog. Exceeding

the storage limit could cause the SCIS application to fail on a device. This limit often affects catalogs of over 20,000 items. See the help topic Fallback and Storage Limits for Mobile Apps for more information on storage limits. This new Fallback feature limits periodic catalog downloads to your mobile devices to 20,000 item SKUs. You can select the items to include plus rely on a NetSuite script to flag and include items purchased in recent orders. Manually selected items have priority over items flagged due to being recently purchased. Note: The Fallback Open Item feature has become part of the Fallback Catalog Limit feature. Combined, these setups provide a unified solution that ensures your stores are covered in the event of an outage. See the help topics Avoiding Storage Issues by Using a Fallback Catalog Limit and Avoiding Storage Issues by Using the Fallback Open Item. Important: To use the Fallback Catalog Limit feature and also enable Open Item, you must:

  1. Enable the Catalog Limit option
  2. Add the Catalog Limit field sets
  3. Optionally choose specific items to include in Catalog Limit downloads. See the Help Center topic Setting up a Fallback Catalog Limit and Open Item option.

New Application Performance Management (APM) Sensors

We added the following sensors to assist you with monitoring and managing performance at the SCIS point of sale.

  • Customers and Items
    • Apply transaction discount, cart ready — Measures the time used to apply discount at the transaction-level. Starts when user applies discount from the discount form. Ends when user can resume interacting with cart.
  • Log in and Authentication
    • Authenticate login credentials — Measures the time to authenticate login credentials. Begins when user clicks Log In and ends when user selects a role, location, or proceeds directly to the open cart.
  • Payments, Payment Devices, and Refunds
    • Paying with credit memo — Measures time to complete payment tendered using credit memo. Begins when user applies payment. Ends when receipt displays. ▬ Excludes time, if needed, to manually enter credit memo information. ▬ For split payments, ends when ready to apply next payment.
    • Paying with gift card — Measures time to complete payment tendered using gift card. Begins when user applies payment. Ends when receipt displays. ▬ Excludes time spent manually entering gift card information. ▬ For split payments, ends when ready to apply next payment.
    • Priming the payment device for refund — Measures the time spent initializing payment device to accept refund information. Begins when user applies refund payment. Ends with prompt that device is ready to process refund.
    • Refunding automatically to original card — Lists the time required to automatically refund payment to original card used for purchase. Starts when payment device is primed to begin refund. Ends when refund applied to card and receipt displays.
    • Refunding to specific card — Lists the time required to refund a specific card after payment device is primed. Starts when payment device is primed to begin refund. Ends when refund applied to card and receipt displays. This measurement is different from refunds automatically applied to the original purchase card. To view the updated sensor list, see the help topic Action Sensors.

SuiteApp Distribution

SuiteApp distribution includes SuiteBundler, SuiteApp Marketplace, and SuiteApp Control Center capabilities that you can use to distribute customizations to accounts. Advanced Notice: Deprecation of NetSuite Bundle

Repository in 2021.1

As of the January 18, 2021, the NetSuite bundle repository will be deprecated. After your account is upgraded to 2021.1, you will no longer be able to use the bundle repository to install bundles or distribute new bundles. Specifically, the Copy to Repository option will no longer be available on the

Bundle Availability page. You can store bundles in one of your accounts. For unmanaged bundles, you

should instruct your customers to upgrade their bundles to a new version that is stored somewhere other than the bundle repository. For more information, see the help topic Moving a Bundle Out of the Bundle Repository. If you have additional questions or require assistance, please contact NetSuite Customer Support.

Bundle Support During Release Phasing

Bundle support during phasing of 2020.2 is consistent with the support provided during previous

releases. During phasing of 2020.2, some accounts continue to use 2020.1 at the same time that other accounts are upgraded to 2020.2. Therefore, you may be using a different version than some of the accounts where your bundles are installed. Review the following descriptions for a reminder of how bundles from different versions are handled during release phasing:

  • Bundles developed with 2020.1 can be installed in accounts that are already using 2020.2.
  • Bundles developed with 2020.2 can be installed in accounts that are still using 2020.1, but with the following limitations:
    • When a user in a 2020.1 account installs a bundle from a 2020.2 account, the bundle installation stops if there are object types in the bundle that are not supported in 2020.1.
    • A bundle with a script that uses a new API available only in 2020.2 can be installed into a 2020.1 account, but the script may not function correctly because 2020.1 does not support the API. Enhancements to SuiteApp Control Center managers:
  • Server-side filter sorting and pagination – You can view more than 5000 companies on the Install Base page.
  • NetSuite version – You can view and filter the NetSuite version that a customer is running on the Install Base page and the New Upgrade page.
  • Installation count – You can view the number of customers that have installed a particular version of your SuiteApp on the Versions page. You can click the number on the Versions page to be redirected to the Install Base page. On the Install Base page, you can view the details for the customers that have installed a particular version of your SuiteApp. Localization Context Filtering Supported for Workflows in

Bundles

As of 2020.2, localization context filtering is supported for workflows that are included in bundles. If a workflow in a bundle has localization context filtering set up, that filtering works in all target accounts where the bundle is installed. A workflow’s localization context represents the country or countries associated with records on which the workflow is run. Localization context filtering is set up using the Localization Context field on the workflow definition record. This field filters the records on which workflows run, based on the localization context of the records. For example, a workflow that has the localization context of France set on its workflow definition record only runs on records that have a localization context of France. It does not run on records with other localization contexts. However, if a record included in a workflow does not support localization context filtering, the workflow always runs on this record regardless of localization context selected on the workflow definition record.

Localization context filtering supports the following cross-version bundling behaviors:

  • You can bundle a workflow with localization context filtering in a source account running 2020.2 and install it into a target account running 2020.1. The localization context filtering is removed from the workflow because it is not supported in the target account running 2020.1. The workflow behaves as if all countries were selected for localization context filtering.
  • You can bundle a workflow in a source account running 2020.1 and install it into a target account running 2020.2. The localization context on the workflow is set to all countries in the target account running 2020.2. For more information about localization context filtering support for workflows, see Localization Context Available for Workflows. Enhancements to Custom Object Translatable Fields and

Translation Collections Support in Bundles

SuiteBundler supports the 2020.2 enhancements to custom object translatable fields and Translation

Collections. For more information, see Additional Translatable Fields Support for Translation Collection Customizations. This support imposes the following limitations on bundles that include a Translation Collection and custom objects that contain translatable fields that reference translation strings from that Translation

Collection:

  • You cannot install these bundles from a source account running 2020.2 to a target account running 2020.1, or from a source account running 2020.1 to a target account running 2020.2.
  • You can only install such bundles to target accounts running the same NetSuite version as the source account. Note: These limitations do not apply to bundles that include only Translation Collections.

Consider the following when modifying Translation Collections in a bundle:

  • If you delete a translation string from a bundled Translation Collection in a source account, and later you update that bundle in a target account:
    • All references in custom object translatable fields to that deleted translation string from the Translation Collection are unlinked from that deleted translation string in the target account. The unlinked translation string becomes a standalone translation string.
    • Custom object translatable fields retain the original translation string, including the translations, in the target account.
  • If you update a translation string in a bundled Translation Collection in a source account, and a custom object translatable field in a target account that references that translation string fails validation:
    • The custom object translatable field is not updated in the target account and is unlinked from the translation string in the Translation Collection. The unlinked translation string becomes a standalone translation string.
    • The custom object translatable field retains the original translation string, including the translations, in the target account. For more information about translation strings, see the help topic String Hierarchy and Translation String Linking.

SuiteBuilder – Customization

This release note was updated September 2, 2020. New Record Customization Provides Consolidated View of

Record Types

Warning: Record Customization (Beta) is a beta feature. The contents of this feature are

preliminary and may be changed or discontinued without prior notice. Any changes may impact the feature’s operation with the NetSuite application. NetSuite warranties and product service levels shall not apply to the feature or the impact of the feature on other portions of the NetSuite application. NetSuite may review and monitor the performance and use of this feature. The documentation for this feature is also considered a beta version and is subject to revision. Please review Beta Software Legal Notices. ORACLE CONFIDENTIAL. For authorized use only. Do not distribute to third parties. Pre-General Availability Draft: September 25, 2020.

Record Customization provides a consolidated view of all business record types in NetSuite. You can view

and maintain the record types in your account. You can also create new fields and sublists to include on a record.

Having a unified location to set up mandatory fields makes it convenient to maintain mandatory settings

for multiple fields at one time. When you make a field mandatory, the change is automatically saved to the server and applies to all platform channels, such as workflow, forms, and so on. Record Customization mandatory settings apply to all other forms. For example, if you make a field mandatory in Record Customization, the field is marked as mandatory on all forms that include the field. The access control overview in Record Customization provides you with a view of the roles and employees that have access to a specific record or field. You can view a list of all users with access to a record or field as well as the level of access the users have. Additionally, you can view information about applied record restrictions on a role. From the access control overview, you can also maintain roles and user access. For more information, see the help topic Record Customization (Beta).

Custom Segments Enhancements

Two enhancements are available for custom segments: a Display Type field has been added to custom

segment configuration, and the Custom Segment field has been renamed Originating Custom Segment. A Display Type field is now available on the Custom Segment definition page. Use this field to select a display type for the custom segment: normal, disabled, or hidden. For information about the display types, see the help topic Creating a Custom Segment. Note: The Display Type field is not supported by SuiteBundler. The Display Type field is set to Normal on any custom segments included in a bundle. The Custom Segment field on the Custom Record Type page has been renamed Originating Custom

Segment. The new field name more accurately reflects the relationship of this custom record type to its

related custom segment. The custom record type is created when the custom segment is created. For information about custom record types that are associated with a custom segment, see the help topic Custom Record Types Associated with a Custom Segment. Translation Collections for Custom Objects Supported in SDF Translation collections for several custom objects can now be managed in SDF using the translationcollection object type. For a complete list of the custom objects supported, see Additional Translatable Fields Support for Translation Collection Customizations. Sales and Purchase Custom Transactions Transformation

Enhancements

Sales and Purchase Custom Transactions have been enhanced to include a new generic link type for transformed transactions and additional transformations. View the New Feature Training for Sales and Purchase Custom Transactions. Previously, when you transformed a custom transaction, the system did not retain information about the source transaction. As of 2020.2, a new generic transformation link is created for transaction transformations that include custom transactions. When the custom transaction is the target transaction, the link appears in the Created From field. When the custom transaction is the source transaction, the link appears on the Related Records subtab. This generic link is created only if a more specific link does not already exist. The link provides a better audit trail on business workflows that include custom transactions. For more information about sales and purchase custom transaction transformations, see the help topic Sales and Purchase Functionality Available in Custom Transactions. Additional transaction transformations are supported by sales and purchase custom transactions. For a complete list of transformations available in sales and purchase custom transactions, see the help topic Sales and Purchase Transaction Types Overview.

Account-Specific Domains Supported in Advanced Printing

NetSuite 2020.2 introduces support for account-specific domains in printing templates. You should use account-specific domains instead of data center-specific URLs. Previously, NetSuite domains were specific to data centers, and links in the printing templates used these data center-specific domains. Links in accounts that moved among data centers did not work. As of 2020.2, printing templates use account-specific domains. With account-specific domains, links work, even if the account is moved from one data center to another.

data center-specific URLs found in printing templates to use the appropriate account-specific domain

URLs for each PDF printout. You should change the URLs in those stored templates to use account-

specific domains. For example, you should change a system.eu2.netsuite.com link in your template link to .app.netsuite.com, where is a variable representing your account ID. If you attempt to create a template using the data center-specific URL format, you will receive a warning message instructing you to use an account-specific domain URL instead. SuiteFlow Redirect Option for Custom Transaction

Transformations

In SuiteFlow, a new Redirect Without Saving box is available on the Transform Record action. You can check this box on a Transform Record action to allow the user to edit the new transaction record before saving. The Redirect Without Saving box lets you use workflows to specify transaction transformation behavior for your custom transactions. For more information, see Redirect Option Available When Setting Transform Record Action Parameters.

Localization of Phone Number Custom Fields

Values in custom fields set to the Phone Number type use localized formatting if the Phone Number

Formatting feature is enabled in your account. The Country field in the subsidiary of the user determines

the local formatting that is applied. For more information, see Introducing Worldwide Support for Phone Number Formatting.