CPQ admin settings

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of CPQ admin settings

    The CPQ admin settings allow administrators to configure how CPQ integrates and interacts with the broader application environment. These settings influence user interface preferences, product identification methods, data synchronization behaviors, and how configuration and BOM data are managed between CPQ and Salesforce.

    Show full answer Show less

    Key Features

    • Admin Version: Enables each administrator to select their preferred UI theme for the CPQ Admin interface. The new Admin UI offers enhanced navigation and color theming, recommended especially when both Configuration Manager and ServiceNow Quote Experience are used. Legacy UI remains available for those preferring the original platform design.
    • Product Id Field: Defines which product identifier CPQ uses for product rules matching. Options include Product Code, Partner Id, or External Id fields from Salesforce. For smoother environment migrations, Product Code or External Id are recommended due to stability across orgs.
    • Roll Up Partner Data: When enabled, CPQ aggregates and averages pricing for items sharing the same partner ID, presenting unique line entries in payloads, which can simplify downstream processing.
    • BOM Types to Include in Save Request: Allows selection or custom entry of BOM (Bill of Materials) types to include when saving configurations via API. Defaults include Sales and Manufacturing BOM types, supporting multi-BOM enhancements.
    • Push BOM and Configuration Data to Salesforce Objects: Two toggles enable CPQ to create records in Salesforce objects (LGK ConfigurationLineItemc for BOM data and LGK ConfigurationFieldDatac for configuration data) upon saving configurations, facilitating data synchronization and reporting.
    • Save Configurations Asynchronously: Controls whether CPQ waits for the save operation to complete before closing the session. Enabling this typically speeds workflows, while disabling can ensure data integrity when many configurations are edited simultaneously.
    • Refresh Token Username: Specifies the user account CPQ uses for API synchronization of configuration and pricing data, including cache population for Product2 and pricebook entries. Resetting this username can help resolve synchronization issues, which occur on a 30-minute interval.

    Key Outcomes

    By configuring these settings, ServiceNow customers can tailor CPQ behavior to their organizational needs, ensuring efficient administration, reliable product matching, accurate BOM and configuration data synchronization, and optimized save workflows. This leads to a smoother CPQ experience that integrates seamlessly with Salesforce data and supports high-volume configuration management.

    Explore the admin settings in CPQ.

    Several settings in CPQ control how CPQ interacts with the rest of your application. To get to the Settings page in CPQ, navigate to the CPQ Admin screen, select the arrow to expand the Utilities section, and then select the Settings tab near the bottom of the menu.

    Admin settings user interface

    1. Admin Version: Determines which UI theme is used for the Admin interface. The setting is maintained at the user level; each administrator can select their preference. If your CPQ environment contains both Configuration Manager and ServiceNow Quote Experience, we highly recommend you use the new Admin UI.
      • The new Admin UI introduces top-level navigation and color theming that helps administrators easily identify and access different administration areas.
      • The Legacy setting retains the administration platform UI used since the application’s inception.
    2. Product Id Field: Determines the field that CPQ uses to match products when using product rules. Select one of the following:
      • Product Code: Corresponds to the Product2.ProductCode field in Salesforce
      • Partner Id: Corresponds to the Product2.Id field in Salesforce
        Note:
        the value of this field will change between environments, such as a Salesforce sandbox org and a production org. For ease of migration across environments, consider using either Product Code or External Id.
      • External Id: Corresponds to the Product2.ExternalId field in Salesforce
    3. Roll Up Partner Data: When enabled, this option combines and averages the price for all items with the same partner ID when responding with easyXDM. This makes each line unique in the payload instead of representing the information individually.
    4. BOM Types to Include in Save Request: Choose BOM types to include in API request when saving the configuration. Select from the menu or type to enter custom BOM types. The default options are Sales and Manufacturing.

      The following video explains how to include multiple BOM types in API requests: Multi BOM Enhancements

    5. Push BOM Data to CPQ Salesforce Object: When enabled, CPQ creates records in Salesforce of the LGK ConfigurationLineItem_c object containing the BOM data when saving a configuration.
    6. Push Config Data to CPQ Salesforce Object: When enabled, CPQ creates records in Salesforce of the LGK ConfigurationFieldData_c object that contains the config data when saving a configuration.
    7. Save Configurations Asynchronously: When disabled, CPQ waits until the configuration is saved in the database before closing the session. When enabled, CPQ starts the save process and immediately closes the session. In most cases, enabling this setting leads to faster workflows, but if a high volume of configurations is being edited simultaneously, disabling this setting ensures that all configurations are saved when returning.
    8. Refresh Token Username: This is the user name that CPQ uses for API syncing of configuration line data, configuration data, and to populate the caches for Product2, pricebook, and pricebook entries.

      Salesforce objects are synchronized every thirty minutes. If you have an issue synchronizing product, pricebook, or pricebook entries, reset the user name and wait thirty minutes to see whether the issue has been resolved.