Revenue-Cloud-Consultant-Accredited-Professional Exam Dumps : Salesforce Revenue Cloud Consultant Accredited Professional (AP-223)

The three common CPQ design mistakes to avoid while implementing CPQ for your customer are:

A. Using price book entries to handle attribute based variationsinstead of lookup price rules: Price book entries are not designed to handle attribute-based variations. Instead, lookup price rules should be used. These rules allow you to adjust pricing based on specific product attributes, providing more flexibility and accuracy1.

C. Creating process builders and flows to pass data between fields instead of using twin field mapping: Process builders and flows can be complex and difficult to maintain. Instead, twin field mapping should be used. This feature allows you to map fields between objects, ensuring data consistency and reducing the need for custom code1.

D. Writing customizations for product selection or validation instead of using option constraints, product rules, and bundles: Customizations can be time-consuming and costly to implement and maintain. Instead, Salesforce CPQ provides built-in features like option constraints, product rules, and bundles that can handle product selection and validation. These features are designed to enforce business rules and ensure that only valid product combinations are selected1.

The error ‘attempt to de-reference a null object’ typically occurs when there is an attempt to access a field or method on an object that has not been initialized or has been assigned a null value. In the context of Salesforce Revenue Cloud, when amending legacy contracts and subscriptions, thiserror can occur if required fields are missing or incorrectly populated on the legacy contract and subscription data. This could be due toincorrect data migration or manual data entry errors. It’s important to ensure that all required fields are correctly populated when migrating legacy data to Salesforce CPQ.

References

Error:Can’t renew the contract automatically because it … - Salesforce

Guidelines for Amending Contracts - Salesforce

Legacy Data Upload for Salesforce CPQ

The correct sequence of evaluation events for a price rule, quote calculator plugin (QCP), and CPQ package pricing engine is as follows:

Internal Initialization: This is the first step where the system prepares for the calculation process.

On Initialization: At this stage, any price rules that are set to trigger ‘On Initialization’ are run.

Calculate Formulas: The system evaluates formula fields.

Before Calculate: Any price rules that are set to trigger ‘Before Calculate’ are run.

Calculate Quantities: The system calculates quantities, for example, bundle components.

On Calculate: Any price rules that are set to trigger ‘On Calculate’ are run.

Price Waterfall Calculation: The system calculates out-of-the-box pricing tools such as block pricing, discount schedules, etc.

After Calculate: Any price rules that are set to trigger ‘After Calculate’ are run1.

This sequence ensures that all calculations and price rules are applied in the correct order, providing accurate pricing information1. References: 

&language=en_US&type=5

&language=en_US&type=1