#Salesforce CPQ & Billing41 personnes en discutent

Hi Rachel - yes, this is very doable with the QCP, and since Year 1 comes in at list you actually have a clean shortcut. Two approaches, depending on exactly what you're upflifting from: 

Common setup for both: order your Quote Line Groups by the group's Start Date so you always know which is Year 1, 2, 3, and match lines across groups by Product (add any configuration attributes to the match key if the same product is configured differently across years). 

Option A - uplift off list (simplest, and it fits your description): because every year holds the same product at the same list price, a compounding 5% is just a per-group markup. The simplest lever is a negative Additional Discount (%), which acts as a markup in CPQ - set it by group in onBeforeCalculate: Year 2 = -5, Year 3 = -10.25. The formula per group is -(1.05^(year-1) - 1) x 100. That lands Year 2 at list x 1.05 and Year 3 at list x 1.1025 - true compounding - and you never have to read another line's calculated price. (Just confirm negative discounts are allowed in your CPQ package settings; if they aren't, set the target Unit Price directly instead.) 

Option B - compound off the prior year's actual (discounted) price: if Year 1 might carry negotiated discounts and you want 5% on the real Year 1 price, do it in onAfterCalculate instead. Build a map of each product's Customer Price (or Net Price) from the prior group, then set this line's price to priorPrice x 1.05. One gotcha worth knowing: CPQ re-derives List Price from the price book during calculation, so don't try to override List - apply your value at the Customer/Net price stage, which is exactly why onAfterCalculate is the right hook here. 

For a straight 'Year 1 at list, +5% each year' setup, Option A is far less code and less fragile, so I'd start there and only move to B if you need to compound off discounted prices. 

(A CPQ Price Rule can handle a flat per-group uplift too, but the compounding across three groups is cleaner to express in the QCP - so your instinct is right.) 

Happy to sketch the grouping/ordering loop if you go with Option A!

Setting the Order Status to Activated should run the triggers and perform the same actions as using the button.  

Note that Order creation runs some async processes that must complete before you Activate. Check the documentation for this. Some of the processes include creating price schedules (if needed) or contracting an amendment (if needed). You may need to build in a delay before triggering activation automatically. There may be some documentation or a knowledge article with more details. 

-Frank 

@Josh Priem

Hi Josh, 

Hello,  I was hoping to get clarity on how I can get I cleaning flip an account from Uplift to List so the renewal picks up new contracted pricing works. For example, you have an account currently with the following:

1. Account
   1. Renewal Pricing Method - Uplift
2. Contracted Pricing Records
   1. Effective Start Date 7/1/2026
   2. Expiration Date 5/31/2027
3. Current contract renewing has a 5% uplift but we do not want that to apply.
4. Subscriptions
   1. Renewal Price - complete
   2. Special Price - complete

When renewing the contract the contract pricing is not being picked up. Why is Contracted Pricing not picked up? I believe it is a couple things:

1. Renewal Pricing Method is Uplift - this may need to switch to List 
2. How can I ensure that the contracted price gets picked up?  Do I need to remove the values from Special Price and Renewal Price?

Just looking for the cleanest way to process this renewal so that it applies the new contracted pricing. 

Thank you.

hi @Deepika Khanna

Thanks for your input. Based on the debug logs, the database deletion is first executed by the Salesforce CPQ managed package through: 

Class.SBQQ.AbstractDAO.deleteByIds: line 237, column 1: 

com.salesforce.api.Database.delete(List<SObject>, Boolean) 

This is immediately followed by: 

Class.SBQQ.QuoteOpportunitySynchronizer.clearOpportunityLineItemsByLineItemId:Delete: List<OpportunityLineItem> 

These log entries confirm that Salesforce CPQ's Quote-to-Opportunity synchronization process is deleting Opportunity Line Items (OLIs) that no longer have a corresponding Quote Line. The deletion is performed by standard managed package logic and not by custom Apex code. 

During synchronization, QuoteOpportunitySynchronizer determines obsolete Opportunity Products and invokes the managed package deletion framework (SBQQ.AbstractDAO.deleteByIds) to remove them from the database. Therefore, the observed OLI deletion is expected CPQ synchronization behavior when reconciling Opportunity Products with the current Quote configuration. 

As you mentioned, To preserve historical product information, preferred approach is to implement an OLI archival solution using a custom history object rather than attempting to prevent CPQ from deleting obsolete OLIs.

Hi @Dasun Kulathilaka

New picklist values are being created as inactive because the integration is adding them through the API without activating them in the picklist value set.  

To resolve this, update the integration so it creates the values as active, or use a post-processing automation to activate new values after they are created. Also, verify that the values are assigned to the required record types, as inactive values won't be available to users even if they exist in the picklist.

Hello!  

For the first question is it how to make a contract that in the system ran from 2021-2026 to actually run form 2023-2028? 

haha yes I would say this org has your work cut out for you. 

Cheers!

Hi @Inbarasu G

, 

The Use Standard Price field on the PriceBookEntry object indicates whether the Price Book Entry is using the Product's Standard Price from the Standard Price Book.

For example, if a product has a Standard Price of $100 and you create a Price Book Entry for a custom Price Book with the same price, Salesforce can use the standard price as the basis for that entry.

In simple terms:

• True → The Price Book Entry uses the Product's Standard Price. 
• False → The Price Book Entry has its own price defined for that specific Price Book. 

This field is also useful when working with custom Price Books, because Salesforce requires a Product to have an active Standard Price before you can add it to a custom Price Book.

Hope this helps!