Product Configurations in NetSuite Commerce: What's New

The product configuration feature allows users to gather selections made for specific configurable items in NetSuite Commerce. These configurations are stored on a configuration record and can be attached to transactions when added. This enables businesses to better manage customizable products and enhances user experience during the purchasing process.

How Do Product Configurations Work?

When a user configures a product, their choices are captured in a configuration record. To access this record, the user can click the Access Config Record button located on the configured item line in transactions. Only users with advanced permissions can view the configuration record and its associated ID.

Setting Permissions

To manage role permissions for accessing configuration records, navigate to the Access subtab on the employee record. Select Advanced in the CPQ Configurator Permissions field to grant the necessary privileges. It's important to note that users assigned an administrator role automatically possess advanced permissions.

Viewing the Configuration ID

Users can also view the configuration ID directly on transactions. This ID can be found within the Configurator Data line field, specifically in the value for the configId parameter.

Managing Configuration Records Through Scripts

The configuration record contents are stored using a compressed format. To retrieve and utilize this configuration data, developers can use a RESTlet endpoint.

Client Scripts

In client scripts, you can make use of the _nHttps.post() method from the N/https module. Below is an example demonstrating how to retrieve the configuration based on its ID:

1"text-purple-400">const response = _nHttps.post({
2  url: _nUrl.resolveScript({
3   scriptId: 'customscript_cpqc_rs_maint',
4   deploymentId: 'customdeploy_cpqc_rs_maint'
5  }),
6  body: {
7   task: 'getConfiguration',
8   configurationId: 501
9  }
10});
11 
12console.log('Parsed configuration: ', JSON.parse(response.body));

Server Scripts

For server scripts, the _nHttps.requestRestlet() method should be used. Here's an example for retrieving the configuration:

1"text-purple-400">const response = _nHttps.requestRestlet({
2  scriptId: 'customscript_cpqc_rs_maint',
3  deploymentId: 'customdeploy_cpqc_rs_maint',
4  method: 'POST',
5  body: {
6   task: 'getConfiguration',
7   configurationId: 501
8  }
9});
10 
11console.log('Parsed configuration: ', JSON.parse(response.body));

This interaction directed through the RESTlet allows for dynamic handling of user-defined configurations, enhancing the customization available in transactions.

Who This Affects

• Administrators: Responsible for setting up permissions for users.
• Developers: Implementing custom scripts to manage product configurations.
• Sales Teams: Utilizing product configurations to tailor offerings for customers.

Key Takeaways

• Product configurations enhance the user experience by allowing customizable items in transactions.
• Access to configuration records is controlled by role permissions, crucial for maintaining data security.
• Developers can retrieve configurations programmatically using RESTlets to enhance functionality.

Source: This article is based on Oracle's official NetSuite documentation.