If Salesforce CPQ hits Salesforce governor limits while configuring a large bundle, it
times out and aborts the configuration process. Enable large configurations in Salesforce CPQ
package settings or individual products to decrease the likelihood of hitting governor limits when
your sales reps configure a large bundle. (Salesforce CPQ Managed Package)
Required Editions
Available in: Salesforce CPQ Summer '18 and later
Enabling large bundle processing causes longer loading times between saving a bundle
configuration and returning to the quote line editor or the next bundle. To avoid unnecessary
loading times in your org, we recommend enabling large bundle processing only if you've already
encountered configuration timeouts.
The number of records that cause a configuration timeout vary by user. However, we've found
that users tend to hit governor limits at around 100 product options in a bundle. Related
records such as option constraints, configuration rules, and configuration attributes also add
to the likelihood of hitting governor limits.
From Setup, in the Quick Find box, enter Installed Packages, and
then select Installed Packages.
Find the Salesforce CPQ package and click Configure.
Click Additional Settings.
Select Enable Large Configurations. Salesforce CPQ will apply large
configuration processing when configuring any of your org's bundles products.
In Salesforce CPQ Summer '19 and later, you can also enable large configurations on
specific bundle parents by selecting the product's Enable Large Configurations field. We
recommend enabling product-level large configurations so that Salesforce CPQ doesn't spend
longer loading times on small bundles that wouldn't otherwise hit governor limits. Users
upgrading to Salesforce CPQ Summer '19 from an earlier version should add Enable Large
Configurations to their product page layout.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.