Welcome to another Salesforce CPQ and Revenue Cloud tutorial. Let’s talk about option constraints. Right now we have a bundle, our canvas backpack, with three different features, minor potions, standard potions, and special potions.
Let’s say for example we only want this special AoE to be selectable if the special damage has already been selected. We’d like to have this option dependent upon this option being selected.
So it should be grayed out unless this one’s been selected. We can use an option constraint to achieve that in Salesforce CPQ. We can also use option constraints for the opposite purpose. So if we only wanted to have one or the other selected, but not both, We could use the same option constraint to achieve either scenario.
Let’s take a look at our parent product. Over here we have our canvas backpack, and in the related list we have option constraints. I happen to have in my memory that those option constraints are numbers 8 and 9, so I’ll go ahead and look for those. And I’ll say we’re going to have this as our special potion require each other.
And then here we’re going to say that the constrained option, so the option that Should be dependent upon the other one is going to be our product number nine. So let’s search for that.
Here we go, let’s search and find number 8. All right, this is going to be active and this is the dependency. So that means that we’re going to require one in order to select the other as opposed to the opposite of that. I’m going to go ahead and save this. And if you’re curious what your option numbers are, you can look here at the option name, and then you can remind yourself which one is numbered accordingly in Salesforce CPQ.
So let’s go back to our quote now. I’m going to cancel out of this configuration, delete this other backpack, and now I’m adding new products. So I’ll choose my bundle again, and when I hit select, You can see that this special AoE is completely grayed out. I can’t select it. So I’ll check the box here and now it’s open and I can check it again.
If I mouse over it, it tells me that special damage is required before I can purchase this. So this is working exactly as expected. Let’s go ahead and see what the opposite scenario looks like, this is something you may find yourself doing when you are doing Salesforce Revenue Cloud Consulting. So if I use the same option constraint right here and I edit this, And we just changed this from Dependency to Exclusion and Save.
We should get the opposite behavior now. So I’m going to cancel out of this one more time. And now we’re going to select that backpack again. This time, if I choose Special Damage, I cannot choose the Special AoE. So now they’re excluding from one another. And that concludes our tutorial on product options in Revenue Cloud.
If you’ve enjoyed this tutorial, please like and subscribe and if you’d like to learn more about this or any other Salesforce CPQ, Revenue Cloud, or Salesforce Revenue Cloud Consulting items – you can work with us. Thank you so much!
Note: The information in this blog post is still applicable to Salesforce CPQ; however, as of Q1 2025, Salesforce CPQ has been officially deemed End of Sale and Salesforce’s new lifecycle management product has been rebranded to Revenue Cloud (previously named RLM). To view the timeline of CPQ and Revenue Cloud history, click here.
If you’d like to know more regarding the differences between Salesforce CPQ and Salesforce’s new offering, Revenue Cloud (RLM), please click here.
