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

 Requirement Overview:

Migrate new CPQ functionality from a sandbox, ensuring that record relationships are preserved.

 Migration Sequence:

Products: Base level of the bundle.

Options: Product Options depend on the Product.

Attributes: Attributes are referenced by Product Options.

Rules: Product Rules depend on Products, Options, and Attributes.

 Steps to Migrate:

Export and import Products first.

Migrate Options, followed by Attributes, and finally Rules.

 Validation:

Test the migrated functionality to ensure all dependencies and relationships are intact.

 Field Location and API Name:

The custom text field Additional_Text__c resides on the Quote object.

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

 Syntax Explanation:

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

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

 Salesforce CPQ Reference:

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

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

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

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

 Requirement:

Apply different uplift rates to Product Families X and Y upon renewal.

 Solution Steps:

Option A: Set the Renewal Uplift Rate on each Subscription record for Product Families X and Y.

Option C: Configure the Account’s Renewal Pricing Method as "Uplift" to enable uplift calculations during renewal.

 Why Other Options Are Incorrect:

B and D: These options fail to apply the correct rates at the Subscription or Product Family level.

 Salesforce CPQ Reference:

Uplift rates and Renewal Pricing methods are outlined in CPQ Renewal Configuration Guidelines ​.

UESTION NO: 83

Users at Universal Containers want to know how Approval requests will be routed prior to submitting a Quote for approval.

How can the admin meet this requirement?

A. Using Native Approvals, build a custom Visualforce Page to display the Approval Process for the Quote.

B. Using Advanced Approvals, place the Preview Approval button on the Quote page layout.

C. Using Advanced Approvals, build a custom Visualforce Page to display the Approval Chains for the Quote.

D. Using Native Approvals, build a custom button to display the approval matrix to users.

Answer: B

 Requirement:

Sales reps need visibility into the Approval Chain before submitting a Quote for approval.

 Solution:

The Preview Approval button in Advanced Approvals allows users to view the Approval Chain directly from the Quote page.

 Why Other Options Are Incorrect:

A and C: Building custom Visualforce pages is unnecessary with Advanced Approvals.

D: Native Approvals do not offer a built-in preview feature.

 Salesforce CPQ Reference:

Advanced Approvals functionality, including the Preview Approval button, is detailed in CPQ Approval Configuration ​.

 Requirement Overview:

Assign generated Approval requests to the user's direct manager.

 Solution:

Salesforce CPQ's Advanced Approvals package includes the setting Next Automated Approver Determined By, which allows Approvals to be routed automatically to the user's manager.

 Steps to Configure:

Navigate to the Approval Process.

Set Next Automated Approver Determined By to Manager.

Save and test the Approval process to ensure it correctly assigns to the manager.

 Requirement:

Set Product A’s price back to its List Price ($300) for a business unit account while ignoring parent account contracted pricing.

 Solution Steps:

Option B: Create a new contracted price record for Product A at $300 for the business unit account.

Option D: Mark the Ignore Parent Contracted Prices checkbox as TRUE on the business unit account to override inherited contracted pricing.

 Why Other Options Are Incorrect:

A: This would affect all contracted prices under the parent account, which is not the desired behavior.

C: Creating a new contracted price with Ignore Parent Contracted Prices set to TRUE is redundant; the account-level setting (D) achieves this.

 Salesforce CPQ Reference:

Contracted Pricing functionality, including parent-child account handling, is outlined in CPQ Pricing Guidelines ​.

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

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

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

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

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

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

 Scenario:

A subscription product does not appear in the Product Selection screen during search.

 Possible Causes:

A: The Active checkbox must be TRUE for the product to appear.

D: The product requires a Pricebook Entry in the corresponding Quote’s Pricebook.

E: If the Component checkbox is TRUE, the product is treated as a bundle component, not standalone, and will not appear in search results.

 Why Other Options Are Incorrect:

B: Cost records are unrelated to product visibility.

C: The Optional checkbox determines bundling behavior, not search visibility.

 Salesforce CPQ Reference:

Product visibility settings are detailed in CPQ Product Selection Configuration ​.

 Requirement:

Maintenance and Support products must display in separate sections during configuration.

Support products should appear above Maintenance products.

 Solution:

Product Features are used to organize Product Options into sections.

The Number field on Product Features determines the order in which the sections appear.

Support should have a lower Number value to appear above Maintenance.

 Salesforce CPQ Reference:

The Product Features Configuration Guidelines explain how to use features and their ordering mechanisms ​.

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

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

 Scenario Breakdown:

Adventure in a Box:

List Price = $10

Discount = 50%

Net Price = $5 (after 50% discount).

Premium Support:

Percent of Total Base = List Price.

Percent of Total = 10%.

 Calculation of Premium Support:

Percent of Total applies to the Net Price of Adventure in a Box.

Net Total of Premium Support = $5 × 10% = $0.50 per month.

For 12 months: $0.50 × 12 = $12.00.

 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

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

 Issue Context:

Some Opportunity Products are not syncing from the Quote, causing pipeline inaccuracies.

 Troubleshooting Steps:

A. Ensure the Quote’s Account lookup is populated:

A missing Account lookup can prevent synchronization as it ties the Quote to the Opportunity.

B. Ensure the Opportunity’s Primary Quote lookup is populated:

The Primary Quote must be explicitly linked to the Opportunity for synchronization to occur.

E. Check the Quote’s Primary checkbox for a value of True:

Only the Primary Quote syncs Opportunity Products. Ensure the checkbox is set to True.

 Validation:

Verify that Opportunity Products sync correctly after ensuring these fields are properly populated.

 Requirement:

Ensure a Product Rule fires only within a specific bundle.

 Solution:

Associating the Configuration Rule with the Parent Product ensures that the rule executes only during configuration of the specified bundle.

 Why Other Options Are Incorrect:

A, B, C: Associating the rule with Product records, Features, or Options does not scope the rule specifically to the parent bundle.

 Salesforce CPQ Reference:

Configuration Rules and their association with Parent Products are documented in CPQ Configuration Rule Guidelines ​.

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

Control the visibility of fields in the Quote Line Editor.

 Solution:

The Edit Lines Field Set Name special field on the Quote object references the field set used to control which Quote Line fields are visible in the editor.

 Steps to Configure:

Navigate to the Field Set on the Quote Line object.

Add or remove fields from the field set referenced in the Edit Lines Field Set Name field.

 Validation:

Test the Quote Line Editor to ensure only the configured fields are visible.

 Requirement:

A unique license number needs to be stored on the Asset record for each unit of a downloadable product sold.

 Solution:

Setting the Asset Conversion field to One per Unit ensures that an individual Asset record is created for each unit of the product. This allows each Asset to store a unique license number.

 Why Other Options Are Incorrect:

A & B: Null or custom values do not enforce one Asset per unit, making it impossible to assign unique license numbers.

D: One per Quote Line creates only one Asset for the entire Quote Line, which is not suitable for unit-level licensing.

 Salesforce CPQ Reference:

The behavior of Asset Conversion is detailed in CPQ Asset Configuration documentation ​.

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

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

 Requirement:

Ensure the Warranty Period from the Product is correctly transferred to the Asset record.

 Solution:

Create a twin field on the Quote Line because:

The Quote Line stores product-specific information during quoting.

When the Quote is contracted, the twin field ensures the value is passed to the Order Product and then to the Asset record.

 Why Other Options Are Incorrect:

A: The Product Option is used within bundles and does not directly transfer to the Asset.

B: The Order Product receives data from the Quote Line, so the twin field must originate there.

C: The Opportunity Product is not involved in the CPQ twin field data flow.

 Salesforce CPQ Reference:

Twin fields and their data flow from Quote Line to Asset are detailed in CPQ Field Mapping 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.

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:

Provide 80 products for general access while restricting access to 20 special products for a specific user group.

 Solution:

Two Price Books:

General Access Price Book: Includes only the 80 products available to all users.

Special Access Price Book: Includes all 100 products for users with elevated access.

Guided Selling: Dynamically assigns the appropriate Price Book based on user access level, ensuring visibility is controlled.

 Salesforce CPQ Reference:

The Price Book strategy with Guided Selling is detailed in the Product and Price Configuration guidelines ​.

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

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

Hide products with the Product Family "Software" when a Configuration Attribute is set to "Perpetual."

 Solution:

Use an Error Condition to evaluate the Product Family value on the Product Option record.

Configure a Product Action to Show all products except those with the Product Family "Software."

 Mechanism:

The Error Condition evaluates the Configuration Attribute's value against the Product Option.

The Product Action ensures visibility is dynamically controlled based on the evaluated condition.

 Salesforce CPQ Reference:

Error Conditions and Product Actions are key components of Product Rules in CPQ to implement dynamic product behavior ​.

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

Track individual serial numbers for each unit of Product A sold.

 Solution Details:

Asset Conversion Field determines how assets are created from Quote Lines.

Setting Asset Conversion to One Per Unit creates one Asset record for each unit sold, allowing tracking of individual serial numbers.

 Implementation:

Navigate to the Product Record for Product A.

Set Asset Conversion to One Per Unit.

 Justification:

This setup aligns with Salesforce CPQ's approach for granular tracking of Assets associated with product sales​​.

 Real-Time Calculation:

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

 Field Behavior:

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

 Salesforce CPQ Reference:

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

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

Ensure that products available for selection are filtered by the Quote’s currency.

 Solution:

CPQ filters products based on the Price Book Entries associated with the Opportunity/Quote’s currency.

 Why Other Options Are Incorrect:

A: Active currencies do not determine product availability.

B: Dated Exchange Rates do not affect product selection directly.

C: Products with a zero Pricebook Entry are not valid for selection.

 Salesforce CPQ Reference:

Multi-currency product selection is documented in CPQ Multi-Currency Configuration ​.

A. Leverage Salesforce automation to select the Order by Quote Line Group field on the Quote.

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

 Requirement Overview:

Northern Trail Outfitters wants future renewals to be reflected in the Opportunity pipeline as soon as a Contract is created.

 Solution Details:

The Renewal Quoted checkbox ensures that the renewal Opportunity is created and linked to the pipeline when the Contract is generated.

 Steps to Automate:

Use a Process Builder or Flow to automatically set the Renewal Quoted checkbox on the Contract upon creation.

 Validation:

Test the process by creating a new Contract and verifying that the renewal Opportunity is added to the pipeline.

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

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

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

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.

 Requirement Overview:

Display Configuration Attribute X on the configuration page of a bundle and in a Line Item Column on the output document.

 Solution Details:

Product Option: Add the Configuration Attribute X custom field to ensure it appears during the configuration process.

Quote Line: Add the same custom field to enable its display as a Line Item Column in the Quote output.

 Steps to Configure:

Create a custom field named Configuration Attribute X on the Product Option and Quote Line objects.

Add the field to the relevant field sets and templates for visibility in both the configurator and the output document.

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

 Cause Analysis:

Hidden = TRUE: Products marked as hidden do not appear in the Opportunity Line Item after saving the Quote.

Component = TRUE: Products flagged as components are part of a bundle and are not directly added as standalone Opportunity Line Items.

 Key Settings:

These configurations are commonly used for internal or auxiliary products within a bundle or restricted products.

 Salesforce CPQ Reference:

The behavior is explained under Product Configuration and Quote Mapping ​.

 Requirement:

Sales reps need to identify Product Options linked to Quote Lines in the Quote Line Editor.

 Solution:

Enabling Visualize Product Hierarchy organizes Quote Lines based on their position within the bundle, displaying the parent-child relationship.

 Why Other Options Are Incorrect:

A: The Product Option Drawer enables detail viewing but does not organize Quote Lines.

B: Preserve Bundle Structure applies to output documents, not the Line Editor.

D: Keep Bundle Together affects grouping but not hierarchy visualization.

 Salesforce CPQ Reference:

Hierarchy settings are covered in the Quote Line Editor Configuration documentation ​.

When a user performs a contract renewal and finds that the Price Book on the Renewal Opportunity or Quote is incorrect, the issue often arises due to the absence of a Price Book reference on the original Contract. To address this, the Renewal Pricebook ID field on the Contract must be populated. This field ensures the correct Price Book is carried over during the renewal process.

Step 1: Understand the Renewal Pricebook ID Field

Field Location: The SBQQ__RenewalPricebookId__c field is on the Contract object.

Purpose: It specifies which Price Book Salesforce CPQ should use for renewal quotes and opportunities created from the contract.

Without this field populated, Salesforce CPQ defaults to another Price Book, which can lead to inaccuracieste the Renewal Pricebook ID**

Access the Contract Record:

Navigate to the relevant Contract record in Salesforce.

Edit the Contract:

Populate the Renewal Pricebook ID field with the 18-digit Salesforce ID of the desired Price Book.

This ID corresponds to the Price Book you want Salesforce CPQ to apply during renewals.

Save the Changes:

Ensure the field is correctly updated and the changes are saved .

Step 3: **

Attempt the renewal process again by clicking Renew on the Contract.

Confirm that the Renewal Opportunity and associated Quote now reference the correct Price Book.

Step 4: Consider Automation for Future Accuracy

Automate Field Population:Use Process Builder or a Flow to automatically populate the Renewal Pricebook ID field based on the contract's associated Account or Opportunity. This reduces manual errors and ensures consistency.

Data Validation:Enforce validation rules to prevent contracts from being saved without a valid Renewal Pricebook ID .

By ensuring the Renewal Pricebook ID is coesolve the issue of incorrect Price Books during renewals and prevent similar occurrences in the future.

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