This article explains why additional pricing elements cannot be added to a Salesforce Pricing procedure in Revenue Cloud and outlines the process for requesting a limit increase. By default, the Pricing Procedure Builder supports up to 130 pricing elements per pricing procedure version. Once this limit is reached, attempts to save additional pricing elements fail with the following message:
"The limit of 130 pricing elements that can be added to the [procedure name] pricing procedure was reached in the org. Delete a pricing element and try again."
Similar platform-enforced limits exist for other Salesforce Pricing components, including a maximum of 100 list variables per pricing procedure version and 20 entries within a single Map Line Item element. When these thresholds are exceeded, corresponding error messages are displayed.
Limit increases are not available through self-service configuration. Customers must submit a Salesforce Support case to the Revenue Cloud Feature Activation team. Requests are reviewed and assessed for potential performance impacts before any increase can be granted.
Follow the steps below in the order presented. First, attempt to reduce the number of elements in the pricing procedure. If optimization is not feasible and additional capacity is still required, submit a request for a limit increase.
Cause 1: The Pricing Procedure Contains Unused or Consolidatable Elements
1. From the App Launcher, navigate to **Pricing Procedures**.
2. Open the affected pricing procedure referenced in the error message.
3. In the **Pricing Procedure Versions** related list, open the active version to launch the **Pricing Procedure Builder**.
4. Review all elements within the procedure:
* Remove any elements that are no longer referenced by downstream variables, calculations, or write-back actions.
* Consolidate redundant **Price Adjustment Matrix** elements that reference the same lookup table by combining their input rule variables where appropriate.
5. If a **Map Line Item** element exceeds the supported limit of 20 entries:
* Split the mapping logic across multiple sequential Map Line Item elements, or
* Move the mapping logic into a **Decision Table** and reference it through a Price Adjustment Matrix.
6. If the pricing procedure is approaching or has reached the limit of 100 list variables:
* Remove unused resources from the **Resource Manager**.
* Reuse existing list variables when the underlying data structure supports it.
7. Save the changes and activate the updated pricing procedure version.
Cause 2: Business Requirements Exceed the Default Platform Limits
The limits for pricing elements, list variables, and Map Line Item entries are platform-enforced and cannot be modified through self-service configuration. Any increase must be requested through Salesforce Support.
1. Create a Salesforce Support case and select:
* **Product:** Revenue Cloud
* **Topic:** Price Management
2. Include the following information in the case:
* The 15- or 18-character Org ID for each affected organization (production and sandbox environments).
* The specific limit being reached:
* 130 pricing elements per pricing procedure version
* 100 list variables per pricing procedure version
* 20 entries in a Map Line Item element
* The desired new limit value.
* The name of the affected pricing procedure and a business justification explaining why the design cannot be simplified or split into multiple procedures.
* Confirmation that the organization understands and accepts any potential performance impact associated with increasing the limit.
3. Salesforce Support will submit an internal Feature Activation request to the product team for review.
4. Requests are evaluated on a case-by-case basis and approval is not guaranteed.
5. Once Support confirms that the increase has been applied, reopen the pricing procedure version in the Pricing Procedure Builder and retry the operation.
To verify the issue is resolved, reopen the affected pricing procedure version in the Pricing Procedure Builder, add the pricing element that previously failed to save, and confirm that the procedure can be saved successfully without receiving the following error:
> "The limit of 130 pricing elements that can be added to the [procedure name] pricing procedure was reached in the org. Delete a pricing element and try again."
005385232

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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.