CPQ-Specialist Practice Exam Questions with Answers Salesforce Certified CPQ Specialist (SP25) Certification

? Requirement Overview:

Universal Containers wants to show Quote Line items grouped by Product Family with subtotals for each family in Quote Documents.

? Solution Details:

Salesforce CPQ allows grouping of Line Items in Quote Templates.

Setting SBQQ__ProductFamily__c as the Group field organizes the Quote Lines into separate sections for each Product Family.

? Configuration Steps:

Navigate to the Quote Template.

Create a new Line Items Section.

In the Grouping field, set SBQQ__ProductFamily__c.

Save and test the template by generating a Quote Document.

? Validation:

Confirm that the generated document displays separate tables for Hardware, Software, and Professional Services, with subtotals for each group.

? 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 ?.

In Salesforce CPQ, Product Selection Rules automatically add products to a Quote based on defined conditions. These rules typically evaluate and execute when the Quote is saved, as this triggers the full application of rules and updates to the Quote Lines. Option D aligns with this behavior—saving the Quote ensures the Conference Pass is added. Option A (Configuration Attribute selection) relates to configurator actions, not quote-level rules. Option B (Product selection) triggers option-specific rules, not quote-wide additions. Option C (Quote calculation) updates pricing, not product additions. Salesforce CPQ documentation confirms rule execution on save.

? Requirement:

Render separate Line Item sections for each Product Family and bundle on the output document.

? Solution Steps:

Option B: Create a Line Item section for each Product Family and use the Filter field to display only the relevant products for each section.

Option C: Use a formula field on the Quote Line object to identify the bundle's Name and Number, then set this field in the Group field to group lines within each section.

? Why Other Options Are Incorrect:

A: The Conditional Print field is not used for rendering specific Product Families in Line Item sections.

D: Sort Order on Product records does not meet the grouping and filtering requirements for the output document.

? Salesforce CPQ Reference:

Document generation and Line Item grouping are detailed in Quote Templates Configuration ?.

? Requirement:

Minimize maintenance and ensure scalability for professional services in enterprise server bundles.

New professional services are introduced frequently, requiring dynamic handling.

? Solution Steps:

Dynamic Feature (B): Allows dynamic grouping and population of professional services products, ensuring that new services are automatically included in the configuration without manual updates.

Filter Product Rule (D): Ensures only compatible professional services are displayed by applying a filtering condition with a Product Action.

? Why Other Options Are Incorrect:

A: Custom Actions are useful for guiding users during selection but do not minimize maintenance or scale dynamically.

C: A nested bundle containing all services is cumbersome to maintain as new services are introduced.

? Salesforce CPQ Reference:

Dynamic Features and Filter Product Rules are key tools for managing scalable configurations ?.

? Requirement Overview:

Sales reps want the Square Footage value on a Configuration Attribute to persist when renewing a Quote.

? Twin Field Mechanism:

Twin Fields ensure that data is retained and mapped between related objects.

Creating Twin Fields on the Asset and Subscription objects allows the Square Footage value to be carried forward during renewals.

? Steps to Configure:

Create a custom field for Square Footage on the Asset and Subscription objects.

Ensure the API names of these fields match the Configuration Attribute API name.

Test the renewal process to confirm the value persists.

? Validation:

The Square Footage value should automatically populate in the renewal Quote without manual entry by the sales rep??.

? Requirement Overview:

Universal Containers sells a Product exclusively as part of a bundle and does not want it to appear in the Product Selection screen.

? Solution:

The Component checkbox ensures the Product is only available as part of a bundle and is hidden from the general Product Selection screen.

? Steps to Configure:

Navigate to the Product Record for the item.

Select the Component checkbox.

Save the changes.

? Validation:

Confirm that the Product is not visible on the Product Selection screen but is available within its assigned bundles.

? Dynamic SKU Generation:

A dynamic SKU is created based on user choices during the configuration process. This requires fields that define patterns and positions for combining components into a single SKU.

? Required Fields:

Component Code Position: Determines the position of each component in the SKU.

Component Code: Represents individual product codes that contribute to the SKU.

Configured Code Pattern: Defines the overall pattern of the dynamically generated SKU.

? Salesforce CPQ Reference:

Dynamic SKU creation is described under Configuration and Product Bundling Guidelines ?.

In Salesforce CPQ, amendments adjust subscription quantities incrementally. The original sale (Quote Line and Subscription) is 100. The first amendment reduces to 80, a decrease of 20, so the Quote Line is 80 (absolute), and the Subscription delta is -20 (reflecting the change). The second amendment increases to 120, an increase of 40 from 80, so the Quote Line is 120, and the Subscription delta is 40. Subscription quantities in amendments show the net change (-20, 40) rather than absolute values (80, 120), aligning with CPQ’s amendment mechanics. Option B correctly reflects this: Quote Lines (100, 80, 120) show user-facing totals, while Subscriptions (100, -20, 40) show deltas. Salesforce CPQ documentation explains this behavior in amendment scenarios.

? Requirement:

Universal Containers wants to control whether the Additional Discount column appears on the Quote Template.

? Solution:

By creating a custom checkbox field (Show_Discount__c), administrators can dynamically control the visibility of the Additional Discount column.

This checkbox is referenced in the Conditional Print Field of the Quote Template Line Column settings for the Additional Discount column.

? Mechanism:

When the Show_Discount__c checkbox is TRUE, the column appears.

When FALSE, it does not display.

? Salesforce CPQ Reference:

Conditional Print Field functionality in Quote Templates allows for dynamic content visibility based on field values ?.

? Requirement Overview:

Universal Containers wants to update the Quantity of a specific Product in the Quote Line Editor via a Price Rule.

The Price Rule should target only this specific Product.

? Key Mechanism:

Use a Price Condition on the Price Rule to evaluate a Quote Line field that uniquely identifies the Product (e.g., Product Code or Product Name).

? Steps to Configure:

Navigate to the Price Rule.

Add a Price Condition:

Field: Select a field from the Quote Line that identifies the Product.

Operator: Equals.

Value: Enter the unique value (e.g., Product Code or Name).

Configure the Price Action to update the Quantity field.

? Validation:

Test the rule by adding the specific Product to a Quote and confirming that the rule updates its Quantity as expected.

? 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.

? Requirement Overview:

A group of users should receive Approval requests simultaneously, and only one user's response is required to approve.

? Key Configuration:

Use a Group ID to associate the group of approvers.

Setting Unanimous = False ensures that only one approval is needed to proceed.

? Steps to Configure:

Navigate to the Approver Record related to the Approval Rule.

Reference the appropriate Group ID.

Set the Unanimous checkbox to False.

? Validation:

Test the Approval process by submitting a Quote for approval and confirming that one approval suffices.

Requirement:

Implement a price change for Product A when its quantity exceeds 10.

Solution:

Price Conditions:

Verify that the product is Product A.

Check that the quantity of Product A exceeds 10 using a Summary Variable.

Price Action:

Inject the value $50 into the Unit Price field for Product A.

Why Other Options Are Incorrect:

B, C, D: These options involve unnecessary actions, such as injecting values into the Quantity field, which is unrelated to the requirement.

Salesforce CPQ Reference:

Configuring Price Rules with Conditions and Actions for specific scenarios ?.

? Requirement Overview:

Reduce scrolling in the configurator for a bundle with many Features and Options.

? Solutions:

A. Option Selection Method = Add: Allows users to select options from a pop-up window instead of scrolling through the configurator.

D. Group Features into Tabs: Use the Category field to group Features into tabs for easier navigation.

E. Option Layout = Tabs: Configure the bundle to display Options in a tabular format, reducing scrolling.

? Steps to Configure:

Set the Option Selection Method to Add on relevant Product Features.

Populate the Category field on Product Features to group them into tabs.

Change the Option Layout on the bundle Product to Tabs.

? Validation:

Test the configurator to ensure the layout reduces scrolling and improves usability.

? Requirement Overview:

When renewing Contracts with Premier Support, it must automatically be replaced with Premier Pro.

? Solution:

The Renewal Product field on the Product record allows admins to specify a replacement Product for renewals.

? Steps to Configure:

Navigate to the Premier Support Product record.

Populate the Renewal Product field with Premier Pro.

Save and test the renewal process to confirm Premier Pro replaces Premier Support on the Quote.

? Validation:

Ensure all renewal Quotes replace Premier Support with Premier Pro automatically.

Requirement:

Prevent users from reconfiguring a bundle after its initial configuration.

Solution:

Set Configuration Type to Allowed to permit configuration during initial setup.

Set Configuration Event to Add to allow configuration only when the product is added, blocking reconfiguration later.

Why Other Options Are Incorrect:

A: Disabled blocks all configuration, including initial setup.

B: Configuration Event = Always allows continuous reconfiguration.

D: Reconfigure Line Custom Action is unrelated to this requirement.

Salesforce CPQ Reference:

Configuration Type and Event settings are documented in Bundle Configuration ?.

? Requirement:

When a fixed bundle is selected, users should bypass the configuration process entirely.

? Solution:

Setting the Configuration Type to Allowed ensures users can configure the bundle if necessary.

Setting the Configuration Event to Always skips the configuration process automatically for preconfigured bundles.

? Why Other Options Are Incorrect:

A: Setting Configuration Type to Disabled prevents any configuration, which may not align with future flexibility requirements.

B: Required forces configuration instead of skipping it.

D: Configuration Event = Add requires the user to manually trigger the process during addition.

? Salesforce CPQ Reference:

Bundle Configuration Settings and their implications are detailed in CPQ Configuration Guidelines ?.

? Subscription Product Configuration:

Product B uses the Percent of Total pricing model based on Product A's Net Price.

Product B's Percent of Total Base is set to "Net," and its Percent of Total Target is set to Product A.

Product B's Percent of Total (%) is configured as 10%.

? Calculation:

Product A Net Total = $2,400

Product B Net Total = 10% of Product A Net Total = 2,400×0.1=2402,400 \times 0.1 = 2402,400×0.1=240.

? Salesforce CPQ Reference:

Percent of Total pricing logic is described under Percent of Total Products ?.

? Requirement:

Use fixed pricing for quantity tiers without additional discounts.

? Solution Steps:

B: Marking the product as Non-Discountable prevents additional discounts.

D: Set the Pricing Method to Block to define fixed prices per quantity tier.

E: Create Block Pricing records to define fixed prices for each quantity tier (e.g., 1-5 licenses = $1,000).

? Why Other Options Are Incorrect:

A: Fixed Price is not suitable for tiered pricing.

C: Slab Discount Schedules are not used for block pricing.

? Salesforce CPQ Reference:

Tiered and Block Pricing setups are detailed in Pricing Configuration ?.

? Subscription Term and List Price:

Subscription Product A has a Subscription Term of 6 months with a List Price of $100.

When added to a Quote with a Term of 12 months, the List Price is prorated to account for the longer term.

? Proration and Ranged Discount Schedule:

A Ranged Discount Schedule applies discounts based on quantity, volume, or term thresholds.

For the 12-month term, the price is prorated to $200 (2 times the List Price for 6 months).

The Discount Schedule applies a 25% discount to the prorated price, reducing it to $150.

? Regular Price Calculation:

The Regular Price reflects the discounted value after applying the Discount Schedule:Regular Price=200×(1?0.25)=150×0.5=75\text{Regular Price} = 200 \times (1 - 0.25) = 150 \times 0.5 = 75Regular Price=200×(1?0.25)=150×0.5=75.

? Key Salesforce CPQ Reference Points:

Ranged Discount Schedules modify the List Price based on configured thresholds .

Subscription Pricing Logic ensures correct proration for products with terms different from the Quote Term .

? Requirement:

Allow users to generate output documents in Microsoft Word format.

? Solution:

The Allow Output Format Change checkbox in User Settings enables users to select alternative formats like Microsoft Word during document generation.

? Why Other Options Are Incorrect:

A: The checkbox is user-specific, not template-specific.

C: Creating a second template is unnecessary when users can dynamically change the format.

D: Template Sections do not control output formats.

? Salesforce CPQ Reference:

Configuring user settings for document generation is detailed in CPQ Quote Templates Documentation ?.

? Scenario:

Product A has no Subscription Pricing, while Product B uses Percent of Total with a shared category.

During renewal, Product A has a Net Total of zero.

? Reason:

When the Renewal Model is set to Asset-Based, only assets tied to the Contract are included in the renewal.

Since Product A has no Subscription Pricing, it is not treated as a subscription and thus has a Net Total of zero.

? Why Other Options Are Incorrect:

B: Product A is not pre-owned in this scenario.

C: The Include Net-New Products in Maintenance setting applies to maintenance scenarios, not standard renewals.

D: Asset Conversion determines asset behavior, not renewal totals.

? Salesforce CPQ Reference:

Renewal behaviors with Asset-Based Models are covered in CPQ Renewal Settings Documentation ?.

In Salesforce CPQ, when search filters are configured with predefined values and visible to sales reps, their interaction with the filter is determined by the filter’s configuration and available operators. The behavior described here is tied to Search Filters in the Product Selection screen, which allow users to refine the list of displayed products based on specific criteria.

Search Filter Configuration:

Predefined Filter Value: Here, the filter is set with a value ("Green").

Operator: The operator “starts with” limits the search to product codes beginning with the text "Green."

Sales Rep Interaction with the Filter:

The visibility of the search filter enables sales reps to view and interact with the criteria during product selection.

Specifically, sales reps have the ability to delete the predefined text to ignore the filter and retrieve a broader or unrestricted product list.

Documentation Alignment:According to Salesforce CPQ guidelines (as referenced in the Salesforce CPQ package settings and user behaviors), if filters are not marked as "required," users can remove or modify the filter values dynamically. This is designed to offer flexibility during quoting while maintaining filter defaults for ease of use.

The interaction described above aligns with Salesforce CPQ's behavior regarding visible search filters, emphasizing that sales reps can clear the filter text unless restricted by additional customization.

Use Case Reference:

When a sales rep begins a quote and searches for products, the filter defaults to "Green."

If the rep does not want to limit the product search to codes starting with "Green," they can simply remove the text and refresh the results.

Relevant Salesforce CPQ References:

Search Filters in the Quote Line Editor section of CPQ documentation .

Guidelines for Search Filter Configuration and behaviors when visible filters are not required .

? Requirement Overview:

Limit users from selecting more than 10 product options within a specific Product Feature.

? Key Mechanism:

The Max Options field on the Feature record limits the maximum number of product options that can be selected for that feature.

? Steps to Configure:

Navigate to the Feature Record associated with the Product Bundle.

Set the Max Options field to 10.

Save and test by adding the Product Bundle to a Quote.

? Validation:

When a user attempts to select more than 10 product options within the feature, Salesforce CPQ will prevent further selections and display an appropriate message.

? Bundle Configuration:

Small Storage Container (Option 1): $2.00 × 10 = $20.00

Shipping (Option 4): $7.50 (bundled).

Other Options (Option 2 and Option 3):

Medium Storage Container: Not selected.

Custom Box Label: Not selected.

? Calculation:

Bundle Parent Product Price: $5.00

Total Price: $5.00 (bundle) + $20.00 (Option 1) + $7.50 (Option 4) = $25.00

? Why Other Answers Are Incorrect:

A: Ignores bundled Option 4 price.

C: Includes non-selected options in the total.

D: Excludes all Option prices, which is inaccurate.

? Salesforce CPQ Reference:

Bundling logic and pricing are covered under Bundle Configuration Guidelines ?.

? Issue Context:

Lookup Price Rules rely on the SBQQ__LookupObject__c field to reference the target object (e.g., Rental Rates).

If this API name is inaccurate or incorrectly input, the rule will fail to retrieve the desired value.

? Review Steps:

Go to the Price Rule record.

Check the SBQQ__LookupObject__c field. Confirm the API Name of the Rental Rates object is accurate.

Example: Ensure the API name matches exactly (e.g., Rental_Rates__c).

? Additional Checks:

Verify the Lookup Queries. Ensure the filter conditions correctly target a valid record on the referenced object.

? Salesforce Documentation Reference:This behavior follows Salesforce CPQ's guidelines on Lookup Price Rules configuration??.

? Dynamic Features:

A Dynamic Feature allows administrators to automatically update or populate Product Options for a bundle based on defined rules and conditions.

? Filter Product Rules:

Applying a Filter Product Rule ensures that only relevant or newly available products appear as options for the bundle. This reduces manual maintenance while keeping the bundle dynamic.

? Salesforce CPQ Reference:

Dynamic Features and Filter Product Rules are part of advanced bundling techniques documented under Product Configuration ?.

? Requirement Overview:

Configure tiered pricing for Product A specific to a customer for all future Quotes.

? Solution Details:

Use a Discount Schedule with tiered pricing.

Assign the Discount Schedule to a Contracted Price record tied to the customer's Account.

? Steps to Configure:

Create the Discount Schedule with the desired tiers.

Navigate to the customer’s Account.

Create a Contracted Price record:

Reference Product A.

Assign the Discount Schedule.

? Validation:

Generate a Quote for the customer and confirm the tiered pricing is applied correctly.

? Considerations for Authorizing Calculation Service:

The Calculation Service must be authorized by a user who has sufficient privileges and stable permissions.

? Solution Steps:

Option B: Use a non-human admin user (e.g., an integration user) to authorize the Calculation Service. This ensures consistent access and avoids disruptions due to personnel changes.

Option C: Place the user at the top of the Role Hierarchy to ensure full visibility and access across relevant objects.

? Salesforce CPQ Reference:

Proper user configuration for the Calculation Service is outlined in the CPQ Authorization Guidelines ?.

Requirement Overview:

A product priced at 100 USD and 95 EUR needs to be included as part of a bundle.

Solution:

Bundled Products: Setting the Bundled field to True ensures the product is included in the bundle's total price.

Configure the Price Book Entries with the required prices for the respective currencies.

Steps to Configure:

Navigate to the Product in the 2019 Price Book.

Set 100 USD and 95 EUR as the Price Book Entries.

On the Product Option, mark the Bundled field as True.

Validation:

Test the bundle by adding it to a Quote and verifying the correct pricing behavior.

===============

? Issue Context:

A Contract could not be created from an Order for a new customer.

? Troubleshooting Steps:

A. Confirm Order Product Activation:

Contracts can only be generated for activated Order Products.

C. Check Apex Jobs:

Errors in the contracting process are logged in Apex Jobs. Review these logs for potential issues.

E. Ensure Subscription-Based Order Product:

Contracts require at least one subscription-based Product on the Order.

? Validation:

Verify that all conditions are met and retest the Contract creation process.

? CPQ Price Calculation Sequence:

The Regular Price is calculated as part of the price waterfall, and several factors influence it.

? Key Contributors:

Prorate Multiplier: Adjusts prices for subscription products based on term alignment.

Contracted Price: Overrides the List Price for specific customers.

Discount Schedules: Apply volume or tiered discounts during price calculation.

? Why Other Options Are Incorrect:

A: Additional Discount Fields apply after Regular Price is calculated.

D: Target Customer Amount is used in quoting, not directly in Regular Price calculation.

? Salesforce CPQ Reference:

Price waterfall and Regular Price contributors are detailed in CPQ Pricing Configuration ?.

? Requirement:

Ensure approval requests are routed to a substitute manager during the original manager's absence.

? Solution:

The Delegated Approver lookup field on the Approver record allows the admin to specify a temporary approver.

Setting the Delegation End field ensures the delegation automatically ends upon the original manager’s return.

? Why Other Options Are Incorrect:

A: Using the Next Approver field for temporary delegation is not the intended functionality.

B: Creating an Approval Rule with start and end dates is overly complex and unnecessary.

D: Replacing the original Approver record risks permanent changes and is not recommended for temporary delegation.

? Salesforce CPQ Reference:

Delegated Approval Settings are documented under Advanced Approvals Configuration Guidelines ?.

Understanding the Requirement:

Universal Containers wants a bundle with pre-selected Product Options.

Sales reps should mostly leave the default configuration as-is but need the flexibility to make changes when required.

Salesforce CPQ Feature Overview:

Configuration Type:

Determines whether sales reps can modify the configuration of a bundle product.

Setting it to Allowed permits the flexibility to configure without mandating it.

Configuration Event:

Defines when the bundle configurator is accessible.

Setting it to Edit prevents the configurator from opening automatically but allows sales reps to access it by clicking the "Reconfigure" link.

Configuration Steps:

Navigate to the Bundle Product record in Salesforce CPQ.

Set the Configuration Type field to Allowed. This ensures the configurator is optional and not enforced.

Set the Configuration Event field to Edit. This enables the configurator to be accessible only upon user action.

Key Behaviors:

With these settings, sales reps can use the default configuration but still make changes if needed by accessing the configurator manually.

The "Reconfigure" link in the quote line becomes available for editing.

Testing and Validation:

Add the bundle to a Quote.

Verify that the configurator does not open automatically.

Check that the "Reconfigure" link is accessible on the Quote Line for editing options.

? Scenario Overview:

A Product Rule triggers the addition of the Conference Pass Product when a related Product is selected.

? Key Trigger Mechanism:

Product Rules with an Action to add products execute as soon as the user selects a Product on the Quote.

? Steps to Verify:

Navigate to the Product Rule for the Conference Pass.

Ensure the Evaluation Event is set to fire On Initialization or Selection.

? Salesforce CPQ Reference:

Product Rules are typically triggered based on user actions such as adding Products or configuring attributes??.

? Requirement:

Automatically apply a 25% discount to a specific Product Option within a bundle.

? Solution:

Option C: The Discounted by Package field ensures that the Product Option inherits discounts applied to the bundle as a whole.

Option D: A Price Rule specifically targeting this Product Option can enforce the 25% discount when it is added to the bundle.

? Why Other Options Are Incorrect:

A: The Option Discount (%) field on the Product Feature applies discounts to all options, not just a specific one.

B: The Option Discount (%) field on the Product Option does not dynamically apply discounts based on specific scenarios.

? Salesforce CPQ Reference:

Configuration and discounting for bundles and Product Options are documented under Bundle Pricing Configuration Guidelines ?.

? 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 ?.

? Requirement Overview:

Limit the Product Options displayed in a bundle based on the service level selected by the user via a Configuration Attribute.

? Solution Details:

Selection Price Rule: Use a Selection Price Rule to dynamically show or hide Product Options based on the selected value of the Configuration Attribute.

Apply Immediately: Ensures that changes based on the service level selection occur in real-time during configuration.

? Steps to Configure:

Create the Selection Price Rule:

Define the Price Rule with a Condition targeting the Configuration Attribute value.

Use a Price Action to show or hide Product Options.

Set Apply Immediately:

Navigate to the Configuration Attribute.

Set Apply Immediately to TRUE.

? Validation:

Test the bundle configuration by changing the service level and verifying the Product Options displayed dynamically update.

? 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 Overview:

Prevent users from making price changes to Quotes or Quote Lines that have already been approved.

? Solutions:

C. Validation Rule:

Create a Validation Rule to block any material changes to approved Quotes or Quote Lines.

D. Product Rule:

Use a Validation Product Rule to prevent edits to pricing fields once a Quote has been approved.

? Steps to Configure:

Validation Rule:

Navigate to Setup > Validation Rules for the Quote and Quote Line objects.

Create rules to restrict edits when the status is set to Approved.

Product Rule:

Create a Validation Product Rule targeting Quote or Quote Line fields.

? Validation:

Test by attempting to edit an approved Quote and verifying the system prevents changes.

Background Context:When amending a contract in Salesforce CPQ, issues with net pricing arise if the amendment impacts existing subscription products. Subscription products often rely on Discount Schedules for calculating discounts, especially when quantity changes. The "Cross Order" field on Discount Schedules ensures discounts account for cumulative quantities across multiple orders or contracts.

Problem Analysis:

The reported issue involves incorrect net pricing specifically when the quantity of existing products is adjusted during contract amendments.

This aligns with the functionality of Discount Schedules, where the total quantity determines the discount applied. Without "Cross Order" enabled, Salesforce CPQ considers only the current order's quantities rather than aggregating across orders.

Root Cause Identification:

Discount Schedule and Cross Order:If the Discount Schedule associated with these products does not have "Cross Order" enabled, any amendments won't consider cumulative quantities. Instead, the system recalculates based on only the new or adjusted quantities, leading to incorrect net pricing.

Supporting Evidence:

Salesforce documentation highlights that Cross Order must be selected in the Discount Schedule for accurate discount calculations across multiple orders or contracts. Otherwise, amendments operate in isolation??.

The feature ensures that ongoing contracts retain accurate pricing based on total historical quantities.

Recommended Resolution:

Navigate to the Discount Schedule associated with the affected products.

Verify and enable the Cross Order checkbox:

Go to Setup > Discount Schedules.

Locate the relevant Discount Schedule.

Edit the schedule and enable Cross Order.

Test the functionality by amending the contract and verifying the net pricing calculations.

Preventative Actions:

For all subscription-based products relying on Discount Schedules, ensure Cross Order is enabled during initial configuration.

Provide training to Salesforce CPQ admins to understand the implications of Discount Schedule settings on pricing.

By following these steps and verifying the Discount Schedule configuration, the issue can be resolved, ensuring consistent and accurate net pricing during contract amendments.

? Requirement Overview:

Ensure that the Configuration Attribute value is retained when reconfiguring a bundle.

? Solution:

Create a twin field on the Quote Line object with the same API name as the Configuration Attribute. This allows the value to persist and be passed between configurations.

? Steps to Configure:

Navigate to Setup > Object Manager > Quote Line.

Create a new custom field with the same API name as the Configuration Attribute.

Test the configuration to ensure the value persists during reconfiguration.

? Requirement:

Ensure that custom field data from original Quote Lines flows into Renewal Quote Lines.

? Solution:

Use twin fields on the Asset and Subscription objects to store and transfer data. Twin fields are automatically mapped during renewal processes, ensuring data flows seamlessly.

? Why Other Options Are Incorrect:

A: A formula field cannot persist data on Renewal Quotes.

B: Automatic mapping does not apply to custom fields without twin fields.

C: A Price Rule is unnecessary when twin fields handle this data flow.

? Salesforce CPQ Reference:

Twin fields and their functionality are described in CPQ Subscription Management ?.

? Issue Context:

The custom field is not being updated by the Price Rule even after enabling triggers in the CPQ Package Settings.

? Root Cause:

After creating new fields or updates, the Post Install Script must be executed to register custom fields in the Calculator Referenced Fields list.

? Solution Steps:

Navigate to Setup > Installed Packages > Salesforce CPQ.

Locate the Post Install Scripts section and click Run.

Test the Price Rule again to verify that the custom field is updated correctly.

? Salesforce CPQ Documentation Reference:

Custom fields must be registered with the calculator for the Price Rule engine to interact with them properly??.

To manage a subset of eco-friendly products for opportunities flagged as eco-friendly while allowing flexibility to include all bundles, follow these steps:

Step 1: Create a Filter Product Rule

Filter Product Rules help define dynamic filtering of products displayed during the quoting process.

Navigate to Product Rules

Go to Salesforce Setup ? Product Rules and click New.

Set the Type to Filter and define a clear Name such as "Eco-Friendly Product Filter."

Configure the Filter Logic

Define the conditions to identify eco-friendly and bundle products.

Use the Conditions related list to target the relevant product fields (e.g., a custom checkbox for eco-friendly products and a type field for bundles).

Example condition:

Field = Eco-Friendly Checkbox

Operator = Equals

Value = True

Step 2: Set up the Product Action

Product Actions define what the rule does when triggered.

Add a Product Action

In the Product Rule, go to the Product Actions related list and click New.

Set the Type to Optional Filter. This allows the system to apply the filter by default but enables users to remove the filter and see all bundles.

Link to Add Products Button

Make sure this action links to the Add Products custom action.

Step 3: Ensure Opportunity Integration

The Opportunity flagged as eco-friendly must drive this behavior.

Custom Field Dependency

Ensure the Opportunity has a field (e.g., Eco-Friendly Checkbox) that can be referenced in the Filter Product Rule or through a related custom formula on the Quote.

Dynamic Behavior

When the Opportunity is flagged, the filter is applied dynamically, displaying only eco-friendly and bundle products in the Add Products dialog.

Step 4: Test and Validate

Test the behavior by flagging different Opportunities as eco-friendly and verifying the Add Products functionality:

Eco-Friendly flag ? Default to eco-friendly products and bundles.

No flag ? All products, including non-eco-friendly bundles, are shown.

Additional Considerations:

Search Filter IntegrationThe Search Filter can complement this approach by providing additional options for users to refine their selections further??.

User TrainingTrain sales reps on how to toggle the filter manually if needed.

This setup allows Universal Containers to meet its business objectives while maintaining flexibility for its sales team?.

? Requirement Overview:

Automatically split Orders by delivery location based on Quote Line Groups.

? Key Configurations:

Order by Quote Line Group: Ensures that each Quote Line Group generates a separate Order.

Ordered Field = TRUE: Triggers the creation of Orders for the Quote Lines.

? Steps to Configure:

Ensure the Order by Quote Line Group field is checked on the Quote.

Mark the Ordered field as TRUE.

Test the Order creation process to verify separate Orders are generated by location.

Comprehensive Detailed Step-by-Step Explanation with all Salesforce CPQ References

To split orders based on product family when creating orders from quotes in Salesforce CPQ, the following steps must be followed:

Enable the Allow Multiple Orders Setting

Navigate to Setup > Installed Packages and locate Salesforce CPQ.

Click Configure, then go to the Orders tab in the CPQ package settings.

Check the Allow Multiple Orders option. This allows multiple orders to be created from a single quote.

This setting ensures that products can be grouped and split into separate orders based on specific criteria like Product Family??.

Set the Order By Field to Product Family

From the object management settings for Quotes, edit the Order By field.

Add "Product Family" as a picklist value if it is not already available.

On the Quote, select Product Family in the Order By field.

Save your changes. When creating an order, Salesforce CPQ will group quote lines into separate orders based on the Product Family??.

Process for Creating Orders

On the quote, select the Ordered checkbox.

Salesforce CPQ will automatically split the quote into multiple orders, grouping quote lines by the Product Family value?.

Notes and Considerations

If some quote lines do not have a value for the field used in the Order By, they will be grouped into one order.

This functionality is available in Salesforce CPQ editions starting from Summer ’16??.

By following these steps, administrators can ensure that similar products are automatically separated into different orders based on their product family.

? Requirement:

Allow customers to return asset Products and receive credit.

? Solution:

Setting the Asset Amendment Behavior to Allow Refund enables the product to be reduced in quantity on an Amendment Quote.

Reducing the Quantity on the Amendment Quote triggers a refund process in CPQ.

? Why Other Options Are Incorrect:

A: Negative quantities are not a supported standard in Amendment Quotes.

C & D: Asset records should not be manually edited as changes must flow through Quotes and Orders.

? Salesforce CPQ Reference:

Refund handling and Asset Amendment Behavior are described in Amendment and Renewal Processes ?.

? Requirement:

Streamline the Quote Line Editor by enabling automatic calculations after each change.

? Solution:

Enabling the Calculate Immediately setting in Managed Package Settings ensures calculations are triggered automatically whenever changes are made in the Quote Line Editor.

? Why Other Options Are Incorrect:

A: The Legacy Calculator setting is outdated and not related to automatic calculations.

B: Quick Calculate is a manual process that does not meet the requirement for automatic recalculation.

? Salesforce CPQ Reference:

The Calculate Immediately Setting is described in the CPQ Managed Package Settings documentation ?.

? Scenario Breakdown:

List Price = $100.00 per unit.

Quantity = 21 units.

Discount Schedule:

First Level (1–11 units): 10% discount.

Second Level (11–21 units): 25% discount.

Third Level (21+ units): 50% discount.

? Slab Discount Calculation:

First Level (1–11 units):

Price = $100 × 10 = $1,000

Discount = 10% = $1,000 × 0.10 = $100

Net = $1,000 - $100 = $900

Second Level (11–21 units):

Price = $100 × 10 = $1,000

Discount = 25% = $1,000 × 0.25 = $250

Net = $1,000 - $250 = $750

Total Net = $900 + $750 = $1,700

? Validation:This matches Salesforce CPQ's standard behavior for Slab Discount Schedules, where discounts are applied per tier.

? Requirement:

Ensure that quotes are recalculated with current information prior to approval without reopening the Quote Line Editor.

? Solution:

Option A: Adding or modifying a field in the Calculating Fields Field Set automatically triggers recalculation for quotes.

Option C: Including the Calculate button on the quote layout provides users with a manual option to trigger recalculation before approval.

? Why Other Options Are Incorrect:

B and D: These require additional customization (e.g., creating a custom Lightning button or Flow) and are not standard CPQ features.

? Salesforce CPQ Reference:

The Calculating Fields Field Set and Calculate Button functionalities are well-documented as standard CPQ tools ?.

? Scenario:

Multiple Approval Chains appear in Advanced Approvals, and the order of completion depends on the Final Approval Step value.

? Behavior:

Advanced Approvals prioritizes chains based on their Final Approval Step value, processing the chain with the lowest value first.

? Why Other Options Are Incorrect:

A: Approval Chains are not completed independently but follow the step order.

B: The display order on the screen does not determine completion order.

C: Lowest Approval Step applies to individual steps, not the entire chain.

? Salesforce CPQ Reference:

Approval Chains and step prioritization are detailed in Advanced Approvals Configuration ?.

? Hierarchy of Discount Schedule Application:Salesforce CPQ applies Discount Schedules based on object precedence.

Contracted Price: Overrides Discount Schedules at the Product or Feature level when specific pricing agreements are in place for an Account.

Product Option: A Discount Schedule on a Product Option takes precedence over one defined at the Product Feature level.

? Key Configurations:

Contracted Price: Navigate to the Contracted Price record and add the Discount Schedule.

Product Option: Assign the Discount Schedule on the Product Option record.

? Validation:

Test configurations to confirm the Discount Schedule is applied at the appropriate level and overrides the Feature-level Discount Schedule.

? Requirement:

Different profiles need to see distinct sets of fields in the Quote Line Editor.

? Solution:

Create two field sets on the Quote Line object, one for each profile.

Use a text formula field named EditLinesFieldSetName on the Quote object to dynamically return the appropriate field set name based on the user’s profile.

? Why Other Options Are Incorrect:

A & B: Field sets must be created on the Quote Line object, not the Quote object.

D: This duplicates C but introduces a typo or incorrect description in the explanation.

? Salesforce CPQ Reference:

Field set configurations for the Quote Line Editor are detailed in CPQ Field Configuration Documentation ?.

? Requirement Overview:

Product A must always be included in the bundle.

Product B should be included by default but can be removed by the user.

? Key Configurations:

Required = FALSE: This ensures that Product B is not mandatory and can be removed by the user.

Selected = TRUE: This includes Product B by default when the bundle is added to the Quote.

? Steps to Configure:

Navigate to the Product Option record for Product B.

Set Required to FALSE.

Set Selected to TRUE.

Save and test the behavior by adding the bundle to a Quote.

? Validation:

Product B should be pre-selected in the Quote Line Editor but can be deselected by the user.

This setup ensures flexibility for Product B while ensuring Product A remains mandatory??.

? Requirement Overview:

Sales reps need to redistribute Order Products across multiple Orders.

? Key Considerations:

Ownership Requirement: Only the Order owner or users with elevated permissions (e.g., Modify All) can edit an Order.

Allow Multiple Orders Setting: This setting must be enabled in the CPQ Orders package to allow splitting or redistributing Order Products.

? Steps to Enable:

For Ownership:

Confirm the sales rep is listed as the owner of the Order.

For Package Settings:

Navigate to CPQ Package Settings > Orders.

Enable the "Allow Multiple Orders" checkbox.

? Testing:

Ensure that the Edit Order Products button is exposed on the Order Page Layout and verify redistribution functionality.