We have a customer that sometimes needs to credit an amount which is calculated based on part of the length of the subscription because the service was not delivered as expected during that time. It should not affect the actual running subscription in terms of start and end date as the subscription was still running during that time.
So for example there is a subscription from 1-1-19 till 31-12-19. From 1-3-19 till 31-3-19 the subscription was not what it should be so customer should get a refund for 1 month in this case.
What would be best practice in this case to calculate the credit amount for the customer?
I would like to figure out how to write the function in the Custom Field Definition Detail next to SBQQ__Account__r.op2_Original_Contract_Date__c
Any help will be much appreciated. Thanks!
'December')&' '&Day(YourDateField)&', '&Year(YourDateField)
This will give you the Month DD, YYYY format.
I am working creating custom Quote Templates in CPQ.
I am creating Content that I can use for my Sections in Salesforce.
I want to pull the shipping information from the quote:
Field SBQQ__ShippingName__c for example
And have that included in my "Shipping Section"
I'm working through the documenation for content:
And I'm not sure where to start for the most part. A template content editor is explained but I don't know where it is, and how to use it.
I'm wondering if I can have a editor like the Quote Terms: Template Bottom or Top where I can section things off and add the fields I need.
Can anyone assist?
I am trying to set up a new price rule and i am not able to set up my advanced condition the way I want to.
I have no clue why. See attached my problem:
I found the issue and to me it doesn't make sense that they did it this way so don't shoot the messanger.
The error is referring to the Index Number. The Index Number is a field on the Price Condition Object but it is not the Condition # Field to which you are referring. You may need to add it to the Price Condition Layout to see if but it is a field that needs to be manually populated by you. Once you have those values set (I just set them as the same number as the Condition # field). You should be able to save your Price Rule exactly as you have it in the screenshot.
SAAS: Discount-value - To be used with CLOUD/SAAS discounts only. This discount based on the $$ volume of the deal, Software only, no more multiplying lines and licenses. Simply base your % discount amount on the total dollar $$ volume of the deal. Refer to the chart below for the % to use. The Chart of Discount %:
5K-9,999K = 5%
10K - 19,999K = 10%
20K - 39,999K = 15%
40K - 199,999K = 20%
200K + = 25%
From what I understand, you want the Discount to be applied on the Quote Total amount if at all the total amount reaches a particular value for (consisting of the only specific set of products [Software Only products]).
If that is the case, maybe you can write a price rule to achieve the same.
Here are a high-level steps to achieve the same:
Step 1: Using Summary Variable, calculate the total Price of all the software products.
Step 2: Use the formula to apply the discount in Price Rules to apply a discount based on the table you mentioned above. Here if you can choose to apply a discount on both Quote Level or Quote line level as well basis you need.
Let me know if there is any confusion or if that helps.
I am being required to "enable quotes" to install a software application. We are in the middle of a CPQ install with another team. Is there any negative impact to CPQ if we "enable quotes"?
Does anyone have any processing speed benchmarks when considering Product Selection Rules vs. Option Constraints?
I have one complicated, configured Product that requires 48 Option Constraints for one specific combination (48 different Options in one Feature should be "excluded"/disabled/invalid if some other Option from a different Feature is chosen).
This same logic could be enforced using a "Remove & Hide" Product Rule with a filter, meaning just 1 Product Action record instead of 48 Option Constraint records.
I recognize that there's a difference in how Product Rules are executed, compared to Option Constraints, but from a processing standpoint.... would one of these alternatives (PR vs OC) represent a significant advantage or disadvantage over the other?
As long as you don't have a large amount of other product rules or a large amount of lookup queries in your product rules, the performance shouldn't be much different.
Putting performance aside, I think it would be easier to administer one product rule vs 48 constraints.
Now I want to filter the list of selectable products to be added to each Opportunity using those fields.
Is it possible? In lightning?
This Trailblazer Community category is specific to the Salesforce CPQ and Salesforce Billing products. If you're looking for assistance with Salesforce, you may have better luck re-posting this in another category.