Product Configurations in NetSuite CPQ
Discover new product configuration features in NetSuite CPQ. This update (January 26, 2026) enhances user configurability and record access.
TL;DR Opening
Starting in the Weekly Update on January 26, 2026, NetSuite enhances the product configuration functionality within the CPQ module. Users can now better manage selections for configurable items, improving transaction integration and user access to configuration records.
Overview of Product Configurations
The product configuration feature in NetSuite CPQ centralizes user selections for configurable items, allowing these configurations to be stored on a dedicated configuration record. When a configurable item is added to a transaction, this configuration record is linked, ensuring accurate data capture.
Accessing Configuration Records
To view a configuration record, users can click the Access Config Record button located on the configured item line within a transaction record. This feature is accessible for users with advanced permissions. Here are some important points regarding permissions:
- Users with an administrator role automatically receive advanced permissions.
- To set specific role permissions, navigate to the Access subtab on the employee record and select Advanced in the CPQ Configurator Permissions field before saving the record.
Retrieving Configuration Data
The configuration record is stored in a compressed format, which can be accessed using RESTlet endpoints through custom scripts. This retrieval is essential for integration with any external systems or custom applications.
Example of Client Script
When employing client scripts to retrieve configuration data, you can use the following syntax using the _nHttps.post() method:
const response = _nHttps.post({
url: _nUrl.resolveScript({
scriptId: 'customscript_cpqc_rs_maint',
deploymentId: 'customdeploy_cpqc_rs_maint'
}),
body: {
task: 'getConfiguration',
configurationId: 501
}
});
console.log('Parsed configuration: ', JSON.parse(response.body));
Example of Server Script
For server-side operations, the _nHttps.requestRestlet() method is preferred. The syntax would look like this:
const response = _nHttps.requestRestlet({
scriptId: 'customscript_cpqc_rs_maint',
deploymentId: 'customdeploy_cpqc_rs_maint',
method: 'POST',
body: {
task: 'getConfiguration',
configurationId: 501
}
});
console.log('Parsed configuration: ', JSON.parse(response.body));
Integration and Use Cases
The ability to retrieve decompressed configuration data allows for seamless integration with various business processes. For instance, a furniture manufacturer could dynamically adjust product offerings based on real-time data, improving customer satisfaction and operational efficiency.
Related Topics
Explore other related functionalities, including:
- NetSuite CPQ Configurator Products
- Previewing Products
- Creating Product Categories
Who This Affects
This update primarily impacts:
- Administrators who manage permissions
- Developers creating custom scripts
- Users interacting with configurable products in transactions
Key Takeaways
- The product configuration feature allows users to save selections and access them in transactions.
- Permissions can be easily managed through the employee record.
- Compression of configuration data aids in performance; RESTlets streamline data retrieval.
- Accessible configuration records promote better user interaction and transaction accuracy.
Frequently Asked Questions (4)
What permissions are required to access configuration records in NetSuite CPQ?
How is configuration data retrieved and stored in NetSuite CPQ?
Does the new product configuration feature in NetSuite CPQ affect transaction records?
Can decompressed configuration data be integrated with external systems?
Weekly Update History (1)
Moved the Working with Product Configurations help topic under NetSuite CPQ Configurator Products.
View Oracle DocsWas this article helpful?