#Salesforce CPQ & Billing36 discussing

I have two items related to reconfiguring bundles and how to handle existing subscriptions and assets. 

Currently we have a bundle configured as below:

1. Bundle Header (Parent) - Product A (renewable subscription that has a price associated with it)
   1. Child Product (product option) - Product B (one-time asset that has a price associated with it).

When added to a quote, since the child is not flagged as Bundled, pricing sits at both lines. The business now wants to re-design the bundle. They want it to look like the following:

1.  Bundle Header (Parent) - Product C (renewable subscription that has a $0 price)
   1. Child Product (product option) - Product A (renewable subscription that has a price associated with it).
   2. Child Product (product option) - Product B (one-time asset that has a price associated with it).

Pricing would sit at each child product line. I was thinking I could just reconfigure the bundle by creating the bundle header and adding Product A as a child and then Product B as a child. And remove the child option (product B) from from Product A (basically breaking the original bundle apart).  

But my concern is existing data that was sold under the current configuration. Do I create subscription bundle headers and then realign the current subscriptions and assets to the new bundle header (adding the Root ID, Required By ID, adjust the product option information on each subscription and asset)? If so, what are the possible risks to amendments and renewals? If this is not the best approach what would you suggest? I can’t create new product codes so I need to use the current products and product codes. 

We have a one time subscription Service product that is part of two bundles. We want to break this apart from the bundles to make it standalone and have it only added on new sales quotes. This Service product is a one-time subscription product.  

For new sales, I need to hide the options within the two bundles and have the product auto added. For amendments, I need the options available for the products being revised but if we are adding one of the two bundles for the first time we need the option for the Service product hidden in both bundles.  

How would i build this? For new sales I am thinking a product selection rule to add the standalone product. For new sales a product selection rule to hide the options. For amendments, how would I approach this? 

Thank you. 

We have a product rule set up as follows in Sandbox and Production. Below is the Current Product Rule Configuration.  

• Type=Selection 
• Conditions Met = All 
• Scope = Product 
• Evaluation Event = Always 
• Evaluation Order = 10 

Error Condition: 

• Tested Object = Quote 
• Tested Field = Boost = True
• Operator = equals 
• Filter Type = Value
•  Filter Value = TRUE 

Price Action 1: 

• Product = Product A 
• Type = Enable 

Price Action 2: 

• Product = Product B 
• Type: Enable & Add 

Price Action 3: 

• Product = Product C 
• Type = Enable & Add 
• Required = True 

Price Action 4: 

• Product = Product C 
• Type = Hide 

Configuration Rule

:  

Product = Bundle 1  

In Sandbox the following is occurring in the Configurator:

• Product A is not appearing
• Product B is not appearing
• Product C is appearing and checked

In Production the following is occurring in the Configurator:

• Product A is appearing
• Product B is appearing and checked
• Product C is not appearing

What the Sales team would like to have happen is:

• Product A is appearing
• Product B is appearing and checked
• Product C is appearing and checked

What correction needs to happen to get this to occur? At a minimum I would think I would delete Product Action 4. 

Thank you. 

Rachel 

Hello, 

I am trying to understand best practice for discount schedules when applying to a brand new sale and when applying to an amendment. Here are the scenarios:

1. New Sale - pulls in current discount schedule. The discount schedule is using either the SBQQ__Quantity__c field or a custom quantity field. Cross Orders is checked true. Some discount schedules have aggregation scope blank and some have aggregation scope set to Product.
2. Amendments - subscriptions lines being pulled in through the amendment process apply the original discount schedule as expected. Any new lines added are applying old discount schedules without a tier. But we want the new discount schedule to apply to new lines. Things to note are in number 1 above the SBQQ__QuoteLineQuantityField__c and the fact that Cross Order is checked as true. I have written a price rule that does the following and is working as expected on the new lines but I am not getting the Discount Tiers. Do I need an additional price rule to apply the tier or do I need to create duplicate Discount Schedules that look at the SBQQ__EffectiveQuantity__c field for amendments?
   1. Price Rule Header
      1. Evaluation Scope: Calculator
      2. Lookup Object: SBQQ__DiscountSchedule__c
      3. Calculator Evaluation Event: Before Calculate
   2. Price Conditions
      1. SBQQ__Existing__c equals false
      2. SBQQ__Product__c not equal to blank
   3. Lookup Query
      1. Query 1
         1. Tested Object: Quote Line
         2. Match Type: Field Value
         3. Tested Field: SBQQ__Product__c
         4. Operator: equals
         5. Lookup Field: SBQQ__Product__c
      2. Query 2
         1. Tested Object: Quote
         2. Match Type: Field Value
         3. Tested Field: SBQQ__PricebookId__c
         4. Operator: equals
         5. Lookup Field: SBQQ__Pricebook__c
      3.   Query 3
         1. Match Type: Static Value
         2. Tested Value: true
         3. Operator: equals
         4. Lookup Field: Active_for_New_Quote_Lines__c
      4.  Query 4
         1. Match Type: Static Value
         2. Tested Value: 2026
         3. Operator: equals
         4. Lookup Field: APricing_Year__c
   4.  Price Actions
      1. Price Action 1
         1. Target Object: Quote Line
         2. Target Field: SBQQ__DiscountSchedule__c
      2. Price Action 2
         1. Target Object: Quote Line
         2. Target Field: SBQQ__DiscountSchedule__c
         3. Source Lookup Field: Id

Thank you. 

I created several custom fields on the Opportunity Contact Role object. I want these fields to be available in the "Add Contact Role" popup that appears when adding a Contact Role from an Opportunity.

I have already added the custom fields to the Opportunity Contact Role Multi-Line Layout, but they are still not displayed in the popup.

Is this popup customizable to show custom Opportunity Contact Role fields? If so, are there any additional configuration steps required? If not, what is the recommended Salesforce approach for capturing custom Opportunity Contact Role field values during contact role creation?

I've attached a screenshot for reference. 

I'm investigating an issue where historical Opportunity Line Items (OLIs)

appear to be deleted when creating a new Quote or performing an Amendment. 

My objective is:

• Retain historical OLIs for audit/reporting purposes.
• Prevent business users from manually deleting historical OLIs.
• Continue allowing CPQ Quote Sync, Amendments, and Renewals to function correctly.

Questions:

1. Is SBQQ.AbstractDAO.deleteByIds() expected CPQ behavior during Quote Sync, Amendments, or Renewals?
2. What is the best way to confirm exactly which records are being deleted by CPQ (OpportunityLineItem vs QuoteLine vs Subscription)?
3. Has anyone successfully implemented logic to protect historical Opportunity Products without breaking CPQ synchronization?
4. Is there a recommended CPQ pattern for retaining historical OLIs while still allowing Quote Sync to update current Opportunity Products?
5. Are there any Salesforce CPQ documented behaviors showing when OLIs are deleted/recreated during sync? 
    
   Any guidance, documentation references, or real-world implementation patterns would be greatly appreciated.

#Salesforce CPQ & Billing