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

ï‚· Requirement:

Ensure a product priced as a Percent of Total has a minimum price of $100.

ï‚· Solution Steps:

Option A: Create a Price Book Entry of $100 to set the minimum price for the product.

Option D: Create a $0 Price Book Entry to handle scenarios where Percent of Total calculation would otherwise drop below $100.

ï‚· Why Other Options Are Incorrect:

B: The custom Percent_of_Total_Target_c field is not used for minimum pricing enforcement.

C: The Percent of Total Constraint field alone does not enforce minimum pricing.

ï‚· Salesforce CPQ Reference:

Percent of Total pricing and minimum price settings are described in CPQ Pricing Configuration ​.

ï‚· Requirement:

Notify users in the Quote Line Editor when approval is required to discourage excessive discounting.

ï‚· Solution:

Use a Product Rule with Alert Action to display a notification or message in the Quote Line Editor when a user exceeds predefined discount thresholds.

ï‚· Why Other Options Are Incorrect:

A: Validation Rules prevent actions but do not notify users.

B: Filter Rules are used for restricting product selection, not notifications.

D: Selection Rules govern product compatibility and are irrelevant here.

ï‚· Salesforce CPQ Reference:

Alert actions in Product Rules are outlined in CPQ Product Rule Configuration

ï‚· Requirement:

Allow users to choose options and define quantities during bundle configuration.

ï‚· Configuration Types:

None (A): Users can freely choose options and set quantities.

Allowed (C): Users can choose options and optionally set quantities.

Required (E): Users must configure the options and define quantities.

ï‚· Why Other Options Are Incorrect:

B: Configurable is not a valid value for the Configuration Type field.

D: Disabled prevents any configuration, which contradicts the requirement.

ï‚· Salesforce CPQ Reference:

Configuration Types are documented under Bundle Configuration Guidelines ​.

ï‚· Scenario Overview:

Asset Conversion is set to One per Unit, so each unit sold creates a separate Asset record.

ï‚· Object Relationships:

During Order and Contract processes:

Order Product: Reflects the total quantity of Product A as a single record.

Asset: Creates two Asset records, one for each unit.

ï‚· Validation:

Confirm that the Asset records show separate entries for each unit sold, while other objects (e.g., Order Product) do not duplicate records.

ï‚· Requirement Overview:

Prevent bundles from being reconfigured in Renewal Quotes while allowing configuration during new or amendment Quotes.

ï‚· Solution:

Use a Custom Action Condition to control when the Reconfigure Line action is available.

Set the condition to exclude Renewal Quotes (SBQQ__Type__c != "Renewal").

ï‚· Steps to Configure:

Navigate to the Custom Action Condition related to the Reconfigure Line action.

Set the condition criteria to ensure the action is only available for non-Renewal Quotes.

ï‚· Validation:

Test by creating Renewal, New, and Amendment Quotes and verifying the Reconfigure Line action behaves as expected.

ï‚· Issue:

Sales reps experience excessive horizontal scrolling to access the Clone and Delete actions in the Quote Line Editor.

ï‚· Solution:

Quote Line Editor Drawers provide a compact and user-friendly way to access actions without excessive scrolling.

ï‚· Steps to Configure:

Navigate to Setup > Custom Actions.

Configure the Clone and Delete actions to appear in the Quote Line Editor drawers.

ï‚· Validation:

Open the Quote Line Editor and confirm that the actions are accessible without horizontal scrolling.

Requirement:

Localize Quote Terms into three selectable languages for the quote PDF output.

Solution Steps:

Step A: Create a picklist field (e.g., Output Language) on the Quote object with language codes (e.g., EN, FR, DE) as values.

Step B: Create Localization records for each Quote Term in all three languages, ensuring the Quote PDF reflects the selected language.

Why Other Options Are Incorrect:

C: "Allow Output in Different Languages" is not an actual managed package setting.

D: Setting the Language field alone does not dynamically manage multiple languages for PDF generation.

Salesforce CPQ Reference:

Localization of Quote Terms is covered in CPQ Multi-Language Configuration Guidelines ​.

ï‚· Root Cause:

The Primary Quote field must be included in the Calculating Fields field set to trigger synchronization between the Quote and Opportunity.

ï‚· Steps to Resolve:

Navigate to Setup > Object Manager > Quote.

Locate the Calculating Fields field set.

Add the Primary field to the field set.

ï‚· Testing:

Change the Primary Quote for an Opportunity and verify that the Quote Lines and Opportunity values sync properly.

ï‚· Salesforce CPQ Reference:

The Calculating Fields field set ensures proper updates between related objects during key actions like recalculations​​.

ï‚· Issue Context:

Users encounter a warning when searching Campaign records in the Quote Line Editor.

ï‚· Root Cause:

For Lookup fields to work correctly in Salesforce CPQ's Quote Line Editor, a Twin Field must exist on the target object (Campaign) with the same API name as the Quote Line lookup field.

ï‚· Solution Steps:

Create a custom field on the Campaign Object with the same API name as the lookup field on the Quote Line Object.

Ensure the field types match (e.g., both are Lookup fields or Text fields).

ï‚· Validation:

Test the functionality by searching for Campaign records in the Quote Line Editor. The warning message should no longer appear.

ï‚· Salesforce CPQ Documentation Reference:

This is a common configuration for CPQ Lookup fields in the Quote Line Editor​​.

ï‚· Requirement:

Ensure the correct Distributor Discount is applied to Quote Lines based on the distributor's Discount_Level__c field value.

ï‚· Solution:

Configurator Scoped Price Rule:

A Price Condition checks whether the SBQQ__Quote__r.Distributor__c field is populated.

If the field is blank, the rule does not execute.

Price Action:

Injects the value of the Discount_Level__c field from the Distributor account into the Quote Line's SBQQ__DistributorDiscount__c field.

ï‚· Why Option A is Correct:

Configurator Scope ensures the rule is evaluated during configuration, applying discounts dynamically as the Quote is edited.

ï‚· Why Option B is Incorrect:

Calculator Scoped Price Rules execute during calculations (not configuration), which may result in delayed discount updates.

ï‚· Salesforce CPQ Reference:

Price Rules and their scopes are documented in the CPQ Pricing Logic Configuration ​.