A Salesforce CPQ implementation can suffer from poor performance due to a large number of active price rules supporting complex pricing requirements. To improve performance in this area, a Revenue Cloud Consultant can consider the following tactics:

Implement lookup price rules where applicable (Option B): Lookup price rules in Salesforce CPQ allow for the mapping of data points on a quote line to data in a custom object, finding a matching record with the same values, and retrieving an associated field value from the matched record1.This can help reduce the number of price rules needed, thereby improving performance1.

Implement Quote Calculator Plugin where possible to replace price rules (Option C): The Quote Calculator Plugin in Salesforce CPQ allows for the addition of extra functionality to the quote line editor with custom JavaScript code2.This can change how calculations are performed and manage page-level security such as field visibility2.By replacing some price rules with functionalities in the Quote Calculator Plugin, the number of price rules can be reduced, leading to improved performance2.

Salesforce CPQ Lookup Price Rules

Salesforce CPQ Quote Calculator Plugin

The steps that an implementation team should take to integrate Revenue Cloud with another system are:

B . Complete a source to target mapping of the fields that will integrate between systems: This step involves defining how data fields in Revenue Cloud correspond to data fields in the external system. It is crucial for ensuring accurate data flow and integration functionality between the systems.

D . Design an architecture view of how data integrates and flows between systems: This involves creating a detailed architectural blueprint that outlines how data will be transferred and managed between Revenue Cloud and the external system. It helps in identifying potential integration challenges and ensuring that the integration supports the business processes effectively.

These steps are based on best practices in systems integration, focusing on data consistency and integrity, along with a structured approach to designing integration flows.

Cross object formula fields are fields that reference data from related objects using lookup or master-detail relationships. They can be useful to display information from parent or child objects without creating custom code or workflows. However, using too many cross object formula fields in a Revenue Cloud project can pose some risks, such as:

Formula field data is not always available during CPQ quote calculation. This means that the formula fields may not reflect the latest values from the related objects when the quote is being generated or updated. This can cause inaccurate pricing, discounts, or taxes. To avoid this, it is recommended to use CPQ fields or custom fields instead of cross object formula fields for quote calculation.12

They are computationally expensive. This means that the formula fields require more processing power and time to evaluate and display the data from the related objects. This can affect the performance and responsiveness of the application, especially if there are multiple formula fields on the same object or page layout. To avoid this, it is recommended to limit the number and complexity of cross object formula fields, and use filters or conditions to reduce the number of records that need to be evaluated.34

They can easily exceed limits if not carefully designed and tested. This means that the formula fields can cause errors or warnings if they exceed the maximum length, number, or level of relationships allowed by Salesforce. For example, a formula field can only reference up to 10 unique relationships and span up to five levels of relationships. If these limits are exceeded, the formula field will not save or display correctly. To avoid this, it is recommended to review the formula field limits and best practices, and test the formula fields in different scenarios and environments.

1: Lookup Price Rule query considerations with Salesforce CPQ [7]

2: Salesforce CPQ Quote Calculation Stages [8]

3: What Is a Cross-Object Formula? - Salesforce [9]

4: Tips for Reducing Formula Size and Complexity - Salesforce [10]

5: Formula Field Limits - Salesforce [11]

Upon noticing unacceptable performance times in Salesforce CPQ, particularly when the primary quote syncs to the opportunity, and identifying the cause as being due to extensive process builders referencing the quote and opportunity alongside other heavy customizations, the recommended strategy is to extend customization using coding best practices to improve scalability. This involves reviewing and optimizing the existing customizations, possibly refactoring process builders into more efficient code-based solutions that are better optimized for performance and scalability. This approach helps in addressing the technical debt and ensures that the Revenue Cloud solution is built on a solid and performant foundation.

Incorrect future invoicing for an amended order product might be caused by the following scenarios:

A .Not contracting the Amendment Order: If the amendment order is not contracted, the changes made in the amendment order will not be reflected in the future invoices. This is because the contract is the legal agreement that specifies the terms of the sale, including the products, quantities, and prices.If the amendment order is not contracted, the original terms of the sale remain in effect, which may result in incorrect future invoicing1.

B .Having a subscription on the Contract be linked to an Order Product with one or more unpaid invoice lines: If there are unpaid invoice lines linked to the order product, it may cause discrepancies in the future invoices.This is because the unpaid invoice lines may still be pending for payment, and if they are not resolved before the amendment order is contracted, the future invoices may not accurately reflect the changes made in the amendment order2.

C .Having a subscription on the Contract be linked to an Order Product with one or more invoice lines in draft: If there are invoice lines in draft status linked to the order product, it may cause inaccuracies in the future invoices. This is because the draft invoice lines have not yet been finalized and may still be subject to changes.If these changes are not finalized before the amendment order is contracted, the future invoices may not accurately reflect the changes made in the amendment order2.