Sales-Admn-202 Salesforce Certified CPQ Administrator Questions and Answers

 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 ​.

 Requirement:

Prevent users from selecting both Product C and Product D in a bundle configuration.

 Solution:

Using an Option Constraint with Type = Exclusion ensures that selecting one product automatically excludes the other.

 Why Other Options Are Incorrect:

A: Dependency constraints ensure one product depends on another, which is the opposite of the requirement.

B & D: Setting Min Options and Max Options in a Product Feature does not enforce mutual exclusivity.

 Salesforce CPQ Reference:

Option Constraints and their configuration are detailed in CPQ Bundling Guidelines ​.

 Requirement Overview:

Users need to define Discount Tiers where the values are treated as the Regular Price instead of amounts deducted from the List Price.

 Solution:

Configure the Discount Schedule to:

Set the Discount Unit to Amount.

Choose All from the Override Behavior picklist.

Select the Use Price for Amount checkbox to treat the tier values as Regular Prices.

 Steps to Configure:

Navigate to the Discount Schedule Record.

Set the Discount Unit to Amount.

Select All from the Override Behavior picklist.

Check the Use Price for Amount box.

 Validation:

Test the Discount Schedule to ensure the defined tier values are treated as Regular Prices.

Scenario:

Renewal Pricing Method is set to List, and the Quote contains standalone fixed-price subscription and non-subscription products.

Behavior:

Discounts from the original Quote are carried forward to the renewal Quote automatically as part of the renewal process, ensuring consistency in pricing.

Salesforce CPQ Reference:

Renewal Quote generation processes consider discounting rules as part of the Renewal Pricing Method ​.

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

 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 ​.

 Requirement Overview:

Universal Containers wants to restrict sales reps to accessing only region-specific Products while allowing managers to access all Products.

 Solution:

C. Price Books per Region: Create a separate Price Book for each region, associating only the relevant Products. Share each Price Book with the respective sales reps.

D. Product Rules: Use Product Rules to hide Products from sales reps outside their assigned regions.

 Steps to Configure:

Price Book Setup:

Navigate to Price Books.

Create a Price Book for each region and associate the specific Products.

Use Sharing Rules to share the Price Books with the appropriate sales reps.

Product Rule Setup:

Create a Product Rule with a Condition to hide Products based on the user’s region.

 Validation:

Test by logging in as a sales rep and verifying that they can only see Products for their assigned region.

 Issue:

Contract creation fails when the Contracted checkbox is checked on an Opportunity.

 Possible Causes:

A: If the Subscription Conversion Behavior is set to None, the product is not converted into a Subscription, preventing the Contract from being created.

B: The Opportunity requires a Primary Quote to generate a Contract, as the Contract details are derived from the Quote.

 Why Other Options Are Incorrect:

C: If the Subscription Pricing field is blank, the product is treated as non-subscription but does not prevent Contract creation.

D: Products with Subscription Pricing = One-time are not converted to Subscriptions, but they do not block Contract creation.

 Salesforce CPQ Reference:

Contract creation requirements and behaviors are documented under CPQ Subscription Management Guidelines ​.

 Scenario:

Product A has a 36-month Subscription Term with a List Price of $36,000.

Product B has a 1-month Subscription Term with a List Price of $2,000.

Quote Subscription Term is 18 months.

 Calculation:

Product A Prorate Multiplier = 18 / 36 = 0.5.

Net Total = $36,000 × 15 × 0.5 = $270,000.

Product B Prorate Multiplier = 18 / 1 = 18.

Net Total = $2,000 × 15 × 18 = $36,000.

 Why Other Options Are Incorrect:

A: The Net Total for Product B is incorrectly inflated.

C: The Prorate Multiplier for Product B should reflect the Quote Term-to-Subscription Term ratio, not default to 1.

 Salesforce CPQ Reference:

Prorated pricing and multiplier calculations are explained in Subscription Pricing Guidelines ​.

 Issue:

The validation error message appears immediately after a user sets a specific value in the Configuration Attribute, even before saving.

 Solution:

Setting Apply Immediately to False ensures that changes in Configuration Attributes do not trigger immediate validations. Instead, validations occur only upon clicking Save.

 Why Other Options Are Incorrect:

A: Evaluation Action does not exist as a field for Product Rule Error Conditions.

C: Changing the Apply Immediately field for Product Options does not affect the Configuration Attribute's behavior.

D: Setting Evaluation Event to Save applies to the rule's scope but does not address Configuration Attribute settings.

 Salesforce CPQ Reference:

Configuration Attribute Settings are explained in CPQ Configuration Attribute 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 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 ​.

 Requirement Overview:

Reference specific Error Condition records in the Advanced Condition field of a Product Rule.

 Solution:

Use the Index field value from the Error Condition record in the Advanced Condition formula.

 Example:

If the Index field value is 1 for a specific Error Condition, reference it as 1 in the Advanced Condition (e.g., 1 AND 2).

 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​​.

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

 Requirement Overview:

Universal Containers needs to attach required PDF documents stored in Salesforce Documents to the Quote output.

 Solution:

Use the Additional Document feature on the Quote Template to include PDF files in the generated output.

 Steps to Configure:

Navigate to the Quote Template.

Create an Additional Document for each required PDF:

Reference the document stored in Salesforce.

Save the Quote Template.

 Validation:

Generate a Quote document and confirm that the Additional Documents are included as attachments.

 Requirement:

Ensure the Support SKU is available only in USD and EUR.

 Expected Behavior:

USD: The product is available and uses the Pricebook Entry's List Price.

EUR: The product is available and uses the Pricebook Entry's List Price.

GBP: The product is unavailable due to the absence of a Pricebook Entry in GBP.

 Why Other Options Are Incorrect:

A & D: These imply product unavailability in all currencies, which contradicts the configuration.

B: GBP would not add the product with a zero List Price due to Pricebook Entry restrictions.

 Salesforce CPQ Reference:

Multi-currency behavior and product availability are documented under CPQ Pricing and Product Management ​.

 Scenario Overview:

List Unit Price: Product A's standard price is $150.

Contracted Price: CK has a contracted price of $100 for Product A.

Discretionary Discount: CK negotiated a 10% discretionary discount for this deal.

 Price Calculation:

List Unit Price remains the standard price of $150.

Regular Unit Price applies the contracted price of $100.

Customer Unit Price: After applying the 10% discretionary discount on the contracted price,Customer Unit Price=100−(100×0.1)=90\text{Customer Unit Price} = 100 - (100 \times 0.1) = 90Customer Unit Price=100−(100×0.1)=90.

Net Unit Price matches the Customer Unit Price for the 10 units being purchased, which is $90.

 Salesforce CPQ Reference:

Salesforce CPQ Contracted Price logic ensures negotiated prices override the List Price, and additional discretionary discounts apply as expected ​.

 Requirement:

Group products in collapsible sections based on Product Family in the Add Products page.

 Solution:

Set the Product Results Group Field Name in Additional Settings to Product Family. This groups products by their Product Family in the Add Products page.

 Why Other Options Are Incorrect:

A: Solution Groups apply to Quote Lines, not the Add Products page.

B: Adding fields to the Search Results Field Set does not enable grouping functionality.

C: The Product Search Plugin is unrelated to grouping.

 Salesforce CPQ Reference:

Configuring product grouping is detailed in CPQ Product Search and Results Configuration ​.

 Requirement Overview:

Universal Containers wants to aggregate the quantities of all Product Options in Feature A to determine the Discount Tier.

 Key Configuration:

Assign the Discount Schedule to the Product Feature itself.

Enable the Cross Orders checkbox to aggregate quantities across multiple orders or contracts.

 Steps to Configure:

Navigate to the Product Feature record for Feature A.

Set the Discount Schedule field to the appropriate Discount Schedule.

On the Discount Schedule, check the Cross Orders box.

 Validation:

Add multiple Product Options from Feature A to a Quote and verify that their quantities are aggregated for discount calculation.

 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 ​.

 Requirement Overview:

Ensure that the Contract Name field is visible to users when initiating an Amendment.

 Key Configuration:

The Active Contract Lookup Field Set on the Contract object determines which fields appear when selecting a Contract for an Amendment.

 Steps to Configure:

Navigate to the Field Set named Active Contract Lookup on the Contract Object.

Add the custom Contract Name field to the Field Set.

 Validation:

Test the Amendment process to confirm that the Contract Name field is visible.

 Scenario Breakdown:

Product A has a base list price of $100.

A quantity of 15 is entered on the quote.

Gold Hardware Maintenance Discount applies because contracted pricing is enabled.

Discount for the quantity range (11–20) is 15% (as shown in the table).

 Net Price Calculation:

List Price = $100

Discount = 15%

Quantity = 15

Net Total Price = $100 × 15 × (1 - 0.15) = $1,275.

 Justification for Selected Discount:According to Salesforce CPQ guidelines, when contracted pricing applies, it takes precedence over other Discount Schedules. The Gold Discount Schedule is therefore applied.

 Testing and Validation:Test the configuration using a sample quote to ensure the correct schedule is applied and the net total price matches the expected value.

 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 ​.

 Requirement Overview:

Enable Renewal Uplift for the Account to adjust pricing for renewals.

 Steps to Configure:

Renewal Pricing Method:

Navigate to the Account record.

Set the Renewal Pricing Method field to Uplift.

Renewal Uplift (%):

On the related Contract record, populate the Renewal Uplift (%) field with the desired percentage increase.

 Validation:

Test the renewal process by generating a Renewal Quote and ensuring the Uplift applies to subscription pricing.

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

Understanding the Issue:

The error message, “Product cannot be refunded. The quantity of Line # cannot decrease without a corresponding update,” occurs because the default behavior prevents a decrease in asset quantities unless explicitly allowed.

Asset Conversion for Product A is set to "One per Unit," requiring each unit to be treated as a separate asset.

Key Salesforce CPQ Setting:

Asset Amendment Behavior:

This field on the Product determines how CPQ handles amendments for asset-based products.

Setting it to "Allow Refund" enables sales reps to reduce the quantity of assets during amendment quotes without generating errors​​.

Configuration Steps:

Navigate to the Product Record for Product A in Salesforce CPQ.

Locate the Asset Amendment Behavior field.

Change its value to Allow Refund.

Save the changes.

Impact of the Change:

Sales reps can now amend the quantity of Product A on amendment quotes.

The system will process the reduction in quantity without triggering an error, as the refund behavior is explicitly enabled.

Verification:

Create an amendment quote for a contract involving Product A.

Adjust the quantity of Product A and confirm that the amendment processes successfully without errors.

 Scenario:

The customer wants to increase the subscription quantity for the last month of the contract. The renewal Opportunity must reflect this change.

 Solution:

Generate an Order from the amendment Opportunity to capture the changes.

Contract the amendment Order to update the Contract.

Refresh the renewal Quote to synchronize the increased quantity.

 Why Other Options Are Incorrect:

B: Terminating the contract with a specific end date is unnecessary for this scenario.

C & D: Deleting Renewal Opportunities or Quotes adds unnecessary manual steps and risks data integrity.

 Salesforce CPQ Reference:

The process for handling amendments and renewals is detailed in Amendments and Renewal Configuration Guidelines ​.

 Requirement Overview:

Show or hide price-related data in the Quote PDF based on the Primary Checkbox field value.

 Solution Details:

The Conditional Print Field on Template Sections enables dynamic visibility.

Add the Primary Checkbox as a reference in the Conditional Print Field for the section containing price-related columns.

 Steps to Configure:

Navigate to the Quote Template.

Locate the section containing price-related data.

Set the Conditional Print Field to reference the Primary Checkbox.

 Validation:

Generate PDFs with the Primary checkbox set to both True and False and confirm the expected visibility of pricing data.

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

 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:Universal Containers needs the quantity of product options in a bundle to automatically scale based on the quantity of the parent bundle product.

 Salesforce CPQ Mechanism:

The Type field on the Product Option allows for specific configuration behaviors.

When the Type is set to Component, Salesforce CPQ automatically multiplies the option's quantity by the bundle product's quantity. This ensures that the dependent options align with the parent bundle quantity.

 Implementation Steps:

Navigate to the Product Option record associated with the bundle.

Set the Type field to Component.

Ensure that other configuration settings, such as quantity constraints, align with the desired outcome.

Test the functionality by adding the bundle to a quote and adjusting the quantity. The option quantities should scale proportionally.

 Relevant Salesforce CPQ Documentation:This behavior is a standard feature in Salesforce CPQ and is documented under Product Bundles and Options Configuration.

 Issue:

Quote Lines on Quote A are grouped incorrectly in the output document.

 Possible Causes:

C: Quote Line Groups: Existing Quote Line Groups on the Quote override the Group Field setting in the template.

D: Group Field in Template Section: The Group Field value in the Line Items template section may cause unexpected grouping.

 Why Other Options Are Incorrect:

A: The Modified By field has no impact on template grouping.

B: Configuration Attributes like location affect product selection, not grouping in Quote templates.

 Salesforce CPQ Reference:

Grouping behavior is explained in the Quote Templates and Line Item Configuration documentation ​.

 Requirement:

To allow sales reps to view a subset of products via a button in the Quote Line Editor.

 Solution:

A Custom Action with a Search Filter is configured to dynamically limit the displayed products.

 Mechanism:

The Custom Action triggers the Product Selection process, with the Search Filter applying criteria to display only the desired subset of products.

 Salesforce CPQ Reference:

Custom Actions and Search Filters are documented as the preferred method to customize product visibility in the Product Selection process .

 Approval Scenarios in Advanced Approvals:Salesforce CPQ Advanced Approvals allows flexible approval processes, including the ability to handle group approvals within a single step.

 Key Features:

Any group member may approve: If this option is configured, approval from one group member is sufficient to move the approval step forward.

All group members must approve: When this option is selected, every group member must approve the request before the step can proceed.

 Configuration Steps:

Navigate to the Approval Rule and ensure that the Approval Chain or Approval Step is configured to support group-based logic.

Specify the behavior for the group in the Approval Step Settings.

 Use Cases:

Use "Any group member may approve" for time-sensitive scenarios.

Use "All group members must approve" for critical approvals that require consensus.

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:

The processor is priced differently when sold as a standalone product versus as part of a laptop bundle.

 Solution:

Marking the processor as Bundled ensures the discounted price applies only when it is part of the laptop bundle.

 Mechanism:

When the Bundled checkbox is TRUE, Salesforce CPQ applies the discounted pricing for bundle components based on the defined Price Book Entry.

 Salesforce CPQ Reference:

Bundled pricing behavior is described in the Product Option and Bundle Configuration Guidelines ​.

 Scenario:

The Create Order button generates an Order with half the Quote Lines, and the Ordered checkbox is selected.

 Outcome:

When the Ordered checkbox is checked, remaining Quote Lines are eligible for a new Order. A second Order will be generated for the remaining lines.

 Why Other Options Are Incorrect:

A: An Order without Order Products is invalid in this scenario.

C: No error is thrown because multiple Orders are allowed from the Quote.

D: Existing Orders are not updated with new Quote Lines.

 Salesforce CPQ Reference:

The behavior of the Create Order button is detailed in CPQ Order Management documentation ​.

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.

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.

Understanding the Requirement:

Universal Containers needs Product Option A to be automatically included with Product B during the configuration.

Sales reps should not be able to remove Product Option A.

Salesforce CPQ Mechanism:

The Required field on a Product Option ensures that it is mandatory within a bundle and cannot be deselected by the user during configuration.

Field Behavior:

When the Required checkbox is selected for a Product Option:

The option is always included in the bundle configuration.

Users cannot remove or modify it unless additional automation (like a product rule) overrides this setting.

Configuration Steps:

Navigate to the Product Option A record associated with Product B in Salesforce CPQ.

Select the Required checkbox and save the changes.

Ensure that no conflicting product or price rules exist that could affect this behavior.

Field Alternatives and Clarifications:

Bundled: Sets the option as a part of the bundle, but this primarily affects pricing (sets price to zero) and doesn't enforce inclusion.

Quantity Editable: Allows control over whether users can adjust the quantity but does not prevent removal.

Selected: Preselects the option during configuration but still allows users to deselect it.

Verification and Testing:

Create a test configuration with Product B as the parent and verify that Product A is always included in the bundle.

Attempt to remove Product A to confirm that it is not possible.

 Requirement:

Restrict the products visible during the configuration of a dynamic bundle.

 Solution:

Use a Default Filter in a Product Rule. This ensures only the specified set of products is displayed in the configurator for the dynamic bundle.

 Why Other Options Are Incorrect:

A: Optional filter is not a valid Product Action.

B: The Show action determines visibility but does not enforce restrictions on selections dynamically.

D: Enable action is used to activate a previously disabled product but does not filter selections.

 Salesforce CPQ Reference:

Dynamic bundles and filtering actions are detailed in CPQ Product Rule Configuration Guidelines ​.

 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 ​.

 Requirement Overview:

Universal Containers wants the Shipping Plus product to appear at the top of the Product Selection list.

 Key Configuration:

The Sort Order field determines the sequence of Products in Product Selection.

Products with lower numerical Sort Order values appear at the top.

 Steps to Configure:

Navigate to the Product Record for Shipping Plus.

Set the Sort Order field to the lowest available value (e.g., 1).

Save and test the configuration in the Product Selection screen.

 Validation:

Ensure that Shipping Plus appears at the top of the Product Selection list.

To update Product Option B’s quantity in real time when Product Option A is selected, a Price Rule must trigger dynamically in the configurator. Option A sets the Evaluation Scope to "Configurator" (for real-time updates during configuration), the Configurator Evaluation Event to "Edit" (triggering when edits occur), and "Apply Immediately" on Product Option B (ensuring its quantity updates instantly). Option B (Calculator scope) applies during price calculation, not real-time configuration. Option C targets Product Option A’s immediacy, but the rule must affect B’s quantity. Option D combines Calculator scope with A’s immediacy, missing the real-time configurator need. Salesforce CPQ documentation supports Configurator scope for real-time updates.

 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 ​.

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.

When amending a contract in Salesforce CPQ, the net pricing of products can sometimes appear incorrect, especially when quantities are adjusted on existing subscriptions. The "Revised Quantity" field on the Subscription record is used during amendments to reflect the updated quantity of a subscription product after the amendment. If this field is set incorrectly or unexpectedly (e.g., manually or via automation), it can override the expected quantity and cause discrepancies in pricing calculations, especially for existing products. This aligns with the scenario where the issue only occurs when quantities are adjusted on existing products. Option B (Price Rule firing On Calculate) could affect pricing but typically wouldn’t target only existing products or cause quantity-specific issues unless explicitly designed to do so. Option C (Price Rule firing Before Calculate) might alter pricing but wouldn’t directly tie to quantity adjustments on amendments. Option D (Discount Schedule with Cross Order unselected) affects pricing tiers but isn’t directly related to amendment quantity adjustments. Per Salesforce CPQ documentation, the "Revised Quantity" field is a key factor in amendment scenarios impacting pricing consistency.

 Requirement:

Certain products should only be available as part of a bundle, not sold separately.

 Solution:

Setting the Component checkbox to TRUE on the Product ensures it is only available as a component within a bundle.

 Why Other Options are Incorrect:

A: Removing Price Book Entries restricts pricing but does not limit availability.

B: Configuration Event field is unrelated to this functionality.

D: Product Rules are not required for this basic configuration.

 Salesforce CPQ Reference:

The Component checkbox functionality is documented under Product Configuration in CPQ ​.

 Requirement Overview:

Admin needs to enable Additional Discounts at both the Quote and Group levels in the Line Editor.

 Solution Steps:

For the Quote Object:

Navigate to Setup > Object Manager > Quote.

Locate the Line Editor Field Set.

Add the Additional Disc. (%) field to the field set.

For the Quote Line Group Object:

Navigate to Setup > Object Manager > Quote Line Group.

Locate the Line Editor Field Set.

Add the Additional Disc. (%) field to the field set.

 Testing:

Open the Quote Line Editor and confirm the visibility of the Additional Discount fields at both levels.

 Requirement Overview:

A customer requires specific pricing for their account.

 Solution:

B. Contracted Price Record:

Directly create a Contracted Price record related to the customer’s Account.

D. Contracted Checkbox:

Select the Contracted checkbox on the Quote record to generate a Contracted Price automatically when the Quote is finalized.

 Steps to Configure:

Option B:

Navigate to the Account and create a Contracted Price record for the specific Product and pricing.

Option D:

On the Quote, select the Contracted checkbox and ensure the Quote is synced to generate the Contracted Price.

 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​​.

Universal Containers requires a dynamic approach to display the Monthly Price column on the Quote Document only when the Payment Terms field is set to "Net 30". Here's how to achieve this:

Step 1: Create a Monthly Price Line Column

Navigate to Quote Templates in Salesforce CPQ.

Select the relevant Quote Template.

In the Line Columns related list:

Create a new Line Column for "Monthly Price."

Configure the desired settings for how the Monthly Price should display in the PDF.

Step 2: Create a Custom Formula Field

Navigate to Setup > Object Manager > Quote.

Create a custom formula field (e.g., Show_Monthly_Price) on the Quote object:

Type: Formula (Checkbox).

Formula Logic: IF(Payment_Terms__c = "Net 30", TRUE, FALSE).

Replace Payment_Terms__c with the API name of the Payment Terms field.

This formula ensures the field returns TRUE only when Payment Terms equals "Net 30."

Step 3: Configure Conditional Print Field on the Line Column

Return to the Quote Template and edit the Monthly Price Line Column.

Set the Conditional Print Field to Show_Monthly_Price.

This links the visibility of the Monthly Price column to the custom formula field you created​​.

Step 4: Validate in Quote Document

Generate a Quote Document for a Quote where Payment Terms are set to "Net 30."

The Monthly Price column should appear in the PDF.

Change the Payment Terms to a value other than "Net 30" and regenerate the document.

The Monthly Price column should not appear.

Step 5: Optional Enhancements

Discard Width When Hidden:In the Monthly Price Line Column, enable this setting to avoid column width adjustments when the column is hidden.

Test Across Use Cases:Validate across different Payment Terms to ensure robust behavior.

By using a combination of the Conditional Print Field and a custom formula field, Universal Containers can dynamically control the visibility of the Monthly Price column​​.

 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:

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.

 Potential Causes:

Component Checkbox: Products marked as Components are typically excluded from being directly selectable in the Product Selection screen unless part of a bundle .

Search Filter: Custom Search Filters on the Add Products button limit the display of products based on criteria such as product attributes or field values.

 Excluded Reasons:

Hidden Checkbox: This is generally used to hide products from the Quote Line Editor, not the Product Selection screen.

Custom Action Condition: While these can limit the Add Products button's visibility, they do not directly affect individual product visibility.

 Salesforce CPQ Reference Points:

Documentation on Product Selection Behavior and Search Filters confirms these behaviors ​.

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.

 Requirement Overview:

Each sales team needs access to a specific subset of products without requiring separate Price Books.

 Solution:

Use multiple bundles with validation Product Rules to restrict access to specific products based on user criteria (e.g., Profile or custom field).

This avoids the need to create and manage separate Price Books for each team.

 Steps to Configure:

Create a bundle for each subset of products.

Use Product Rules to validate and restrict access based on sales team criteria.

 Validation:

Test the Product Selection page to ensure that each sales team can access only their specific subset of products.

 Requirement Overview:

Universal Containers wants to hide lid Products from the Product Selection screen since they are only sold as part of a container Product.

 Solution:

By selecting the Hidden checkbox on the lid Product record, the Product is removed from the Product Selection page while remaining available within bundles.

 Steps to Configure:

Navigate to the Product Record for each lid Product.

Select the Hidden checkbox.

Save the changes.

 Validation:

Verify that the lid Products no longer appear on the Product Selection screen but remain accessible as part of their parent container bundles.

 Requirement:

Sell a non-renewable support SKU in 1-month increments, with the ability to cancel before the agreed end date.

 Solution:

SubscriptionType = One-Time: Ensures the product is treated as a one-time charge, not renewable.

SubscriptionTerm = Number of Months: Allows the quote to define the length of the support agreement.

 Why Other Options Are Incorrect:

A and C: These configurations do not align with the requirement to sell support in defined monthly increments.

D: Marking the product as Renewable contradicts the requirement that the product is non-renewable.

 Salesforce CPQ Reference:

SubscriptionType and SubscriptionTerm fields are detailed in the Subscription Products configuration guide ​.