Salesforce CPQ-Specialist - Salesforce Certified CPQ Specialist (SP25)

ï‚· Field Location and API Name:

The custom text field Additional_Text__c resides on the Quote object.

In Salesforce CPQ, the correct syntax to reference fields in HTML templates is to use the merge field syntax appropriate to the object.

ï‚· Syntax Explanation:

{!quote.Additional_Text__c} directly references the field from the Quote object in a format recognized by the CPQ document generation engine.

Alternative options such as {ISBQQ__Quote__r.Additional_Text__c} reference lookup relationships and do not apply here.

ï‚· Salesforce CPQ Reference:

As per the Quote Template Content documentation, use the merge fields directly associated with the object being utilized in the template ​.

ï‚· Real-Time Calculation:

The Calculate Immediately field in CPQ ensures that pricing calculations occur automatically when changes are made in the Quote Line Editor without requiring manual saving.

ï‚· Field Behavior:

Enabling this field configures CPQ to detect changes to the Partner Discount or other relevant fields and trigger real-time recalculations.

ï‚· Salesforce CPQ Reference:

Configuration settings for real-time pricing calculations are documented in the Pricing and Calculation Package Settings .

ï‚· Requirement:

Migrate existing contracts to a new Product version upon renewal.

ï‚· Solution:

Update the Renewal Product field to specify the new version of the Product.

Enable the Renewal Forecast checkbox on the Contract to ensure renewal Quotes reference the new Product version.

ï‚· Why Other Options Are Incorrect:

B: Changing the Product Lookup on the Subscription directly bypasses standard renewal processes.

C: Selection Product Rules enforce configurations during quoting but are not suitable for renewals.

D: Price Rules do not modify Product references during renewal Quotes.

ï‚· Salesforce CPQ Reference:

Renewal product management is outlined in the CPQ Subscription and Renewal Guidelines ​.

ï‚· Requirement:

Organize quoted products by project milestones and generate a separate Order for each Quote Line Group.

ï‚· Solution:

Use Salesforce automation to set the Order by Quote Line Group field on the Quote. This ensures the system generates separate Orders based on the grouping in the Quote Line Editor.

ï‚· Why Other Options Are Incorrect:

B: Relying on notes is manual and error-prone, lacking automation for generating separate Orders.

C: Validation Rules prevent specific actions but do not help organize Orders by Quote Line Group.

D: Custom picklist fields are unnecessary when Order by Quote Line Group exists as a standard feature.

ï‚· Salesforce CPQ Reference:

The Order by Quote Line Group feature is outlined in Order Management Configuration ​.

ï‚· Requirement:

Deploy Price Rules with Lookup Queries that reference a new Rental Rates object.

ï‚· Best Practices for Deployment Order:

Step 1: Rental Rates: Deploy the object and data it references first to ensure lookup data is available.

Step 2: Price Rules: Deploy Price Rules to establish the logic governing pricing calculations.

Step 3: Price Conditions: These evaluate criteria for the rules to execute.

Step 4: Lookup Queries: Queries must reference both the object and conditions, so deploy them after both.

Step 5: Price Actions: Set last to ensure that the actions triggered by the rules execute correctly.

ï‚· Why Other Options Are Incorrect:

A, B, D: Deploying Lookup Queries or Price Actions before Rental Rates or Price Rules may cause execution errors due to missing references.

ï‚· Salesforce CPQ Reference:

Best practices for deploying CPQ Price Rules and Lookup Queries are detailed in Salesforce documentation ​.

ï‚· Issue Context:

Not all Quote Lines are generating Opportunity Product records during the Amendment process.

ï‚· Possible Causes:

A. Net Total = 0:

Salesforce CPQ does not create Opportunity Products for Quote Lines with a Net Total of zero.

D. Exclude from Opportunity:

If the Product has the Exclude from Opportunity checkbox set to TRUE, it prevents Opportunity Product creation.

ï‚· Steps to Investigate:

Verify the Net Total of the Quote Lines.

Check the Product configuration for the Exclude from Opportunity setting.

ï‚· Validation:

Update the relevant fields and test the Amendment process to ensure all eligible Quote Lines generate Opportunity Products.

ï‚· Scenario:

Original subscription: $600 Net Unit Price × Quantity 10 × 24 months = $14,400.

Refund: Ten months into the contract, 14 months remain unused.

ï‚· Calculation:

Refund amount = ($600 × 10 × 14) ÷ 24 = -$3,500.

Amended subscription refund (Quantity = 0): 14 months refund prorated = -$2,500.

ï‚· Why Other Options Are Incorrect:

A, C, D: The refund calculations either overstate or understate the prorated refund based on the subscription term and remaining months.

ï‚· Salesforce CPQ Reference:

Prorated refunds and subscription amendments are explained in CPQ Subscription Pricing Documentation ​.

ï‚· Requirement Overview:

Universal Containers wants to sell monthly subscriptions and round additional days up to the nearest month when calculating prorated prices.

ï‚· Solution Details:

Subscription Term Unit = Month: Ensures that subscriptions are billed on a monthly basis.

Subscription Prorate Precision = Month: Rounds up additional days to the next month.

ï‚· Steps to Configure:

Navigate to CPQ Package Settings > Subscription and Renewal Settings.

Set the Subscription Term Unit to Month.

Set the Subscription Prorate Precision to Month.

Save and test the configuration by creating a Quote with subscription products.

ï‚· Validation:

Ensure that additional days are rounded up to the next month in the prorated pricing calculation​​.

ï‚· Scenario:

A Price Rule utilizes a Lookup Object and Lookup Queries, and multiple records meet the criteria for a single Quote Line.

ï‚· Behavior:

When more than one lookup record meets the criteria, Salesforce CPQ does not apply any value to the Target Field. Instead:

The Target Field retains its original value.

An error message is displayed in the Quote Line Editor, notifying the user of the conflict.

ï‚· Why Other Options Are Incorrect:

A & D: Salesforce CPQ does not resolve ties by sorting records alphabetically.

C: The system does not apply values based on record creation date.

ï‚· Salesforce CPQ Reference:

Lookup Queries behavior and error-handling are outlined in CPQ Price Rules Configuration Guidelines ​.