NetSuite CPQReference

Making New Items Available for Transaction Fields in NetSuite

NetSuite 2026.1 introduces a feature to automatically add new items to transaction fields based on item creation records, improving efficiency.

·3 min read·NetSuite 2026.1·View Oracle Docs

TL;DR Opening

Starting in NetSuite 2026.1, users can automatically make new items available for transaction fields through item creation records, enhancing item management and transaction efficiency. This change is particularly useful for accounts with numerous items, optimizing workflows for customer transactions.

What's New

In 2026.1, NetSuite has refined its item management system by introducing a feature that allows new items created via item creation records to be automatically added to transaction fields. For accounts with less than 300 items, this feature improves access to new resources by enabling the 'Add new resources to transaction fields' option. To locate this setting, navigate to CPQ > Configurator > Settings, then check the appropriate box under the Submit subtab.

Key Functionality Changes

  • Automatic Addition: New items from item creation records are auto-added to transactions when accounts have over 300 items.
  • Manual Management: In accounts with fewer than 300 items, enabling the 'Add new resources to transaction fields' ensures new items appear in dropdown lists.
  • Role Limitations: This option will not work if users have the Customer Center role on the customer record and if products utilize item creation records.

Handling Limitations

If the outlined conditions are met, a different approach is needed:

  1. Replace item creation records with a standard base item and placeholder additional items.
  2. Mapping Records: These records must be established to attach the item creation records to the product and the additional items properly.

Transaction Processing

Upon saving a transaction:

  • Placeholder items get replaced with actual items generated from the item creation records, reflecting accurate line item details and pricing.
  • Ensure pricing for additional items is manually added to the corresponding records to display accurate transaction amounts.

Implementation Steps

To set this up:

  1. On the Product Record:
    • Clear the Base Item field.
    • Select a placeholder as the new base item.
  2. For Additional Items:
    • Clear the Item Creation Record field.
    • Choose the appropriate placeholders.
  3. Mapping Records: Create a mapping record for each item creation record to define replacements.
  4. Attach Records: Ensure both the product and additional item records reference the correct mapping records.

Best Practices

  • Always keep the base item active by confirming the 'Inactive' box is unchecked.
  • Utilize line field mapping records to ensure customization adheres to your company's specific transaction requirements.

Important Notes

  • Using custom scripts may create compatibility issues with these automatic configurations.
  • Implement necessary checks to facilitate accurate replacements in transactions.

Who This Affects

  • Administrators: Responsible for setting up transaction configurations and mappings.
  • Developers: Need to ensure custom scripts do not conflict with new functionalities.
  • CPQ Users: Will benefit directly from increased efficiency in transaction processing.

Key Takeaways

  • New items can now be automatically made available in transaction fields, enhancing operational efficiency.
  • Proper setup instructions and limitations need to be followed to fully utilize this feature.
  • Consider potential conflicts with custom scripts when implementing automatic item additions.

Weekly Update History (1)

NetSuite CPQadded

Added the Making New Items Available for Transaction Fields help topic under Creating Items Required by the Configuration. This help topic explains how to work with item creation records when your account has fewer than 300 items.

View Oracle Docs
Source: Making New Items Available for Transaction Fields Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?