We’re going to be talking about configuration attributes in Salesforce CPQ at the product feature level. So here’s some information from Salesforce about configuration attributes and a little bit about what each field does. We’re going to be talking about configuration attributes at the product feature level. If we go to our quote – we’re adding our canvas backpack bundle. We have one configuration attribute we talked about in the last video for size at the parent level.
This video is going to walk through at the feature level how to get a product option and we’re going to go about it a little bit differently this time!
I’m going to click through each area as opposed to just having all the tabs on the screen.
– go to our Canvas backpack product (parent product)
– all of the brains of the bundle live at the parent level.
– go to related so that we can see all of the associated configuration
– these are our child products (all of the different potions)
– features: these are our groupings in our bundle previously
Additional items:
– One potion requires the other potion
– a configuration rule states no more than 3 potions per backpack.
So we have a little bit going on here on our product, and parent product. Specifically, we have on our standard potions feature, this configuration attribute. Revenue Cloud really lets you customize your products in this way.
– go to our standard potions feature from our backpack parent (limit of no more than three)
We know where this is associated with, but we’re going to go to the related list again and we can see a configuration attribute. When you do Salesforce Revenue Cloud Consulting, knowing what’s on the related list can be very helpful.
It’s important to note if you’re making this configuration attribute from scratch:
– click on new
– choose configuration attribute (if you’ve enabled global attributes, please ignore this at this level)
In Salesforce CPQ if a global attribute and it is tied out – you’re going to have some funny behavior. We’ll talk about that in our next video in the Revenue Realm series (all about Revenue Cloud), about global attributes.
Choose configuration attribute and fill out all of the information.
– Where do we want this attribute to show up?
– row order: top, middle, or bottom
– column order: left, middle, or right
– position on the screen: either the top or the bottom
In Salesforce CPQ, to apply configuration attributes to all of your child products you can check this box. If you don’t see any of these on the page, then edit the page layout for this configuration attribute object.
For your non global configuration attributes in Revenue Cloud, you can specify the product for this configuration attribute. In our case, it’s going to be the bundle parent (canvas backpack, even though this is also associated with the feature).
For your target field if you don’t see the field listed here:
– edit your configuration attribute object
– include the field that you have created at the product option level
– For the most part that covers our configuration attribute
– close out of here because we have the configuration attribute
go back to our Canvas Backpack under related and we can see all of our options. If we didn’t have these fields already created:
– select edit object,
– create the item for class
– make a new picklist value.
– make sure that all of these values are saved to a global value set
– return to object manager and make the field on quote
– make sure that there’s a pick list for class on the quote line
– Without this step it will appear functional and your data will disappear
Make sure the values match and use global value sets to make sure that the data is always perfect. Use picklist at quote line and product option. Update the target field. When you do Salesforce Revenue Cloud Consulting making sure data matches is a great best practice.
Under parent product select feature and then configuration attribute. Inside of this object, update target field:
– click on setup, then edit object
– under fields and relationships, scroll to the bottom to get to target field
– add a new value by clicking new
– type in the API name of our field (class__C)
– apply it to either just configuration attributes or to global attributes so our quote – we’re adding our canvas backpack bundle.
We have one configuration attribute we talked about in the last video for size at the parent level in Salesforce CPQ. This video is going to walk through at the feature level how to get a product option and we’re going to go about it a little bit differently this time! I’m going to click through each area as opposed to just having all the tabs on the screen.
– go to our Canvas backpack product (parent product)
– all of the brains of the bundle live at the parent level.
– go to related so that we can see all of the associated configuration – these are our child products (all of the different potions)
– features: these are our groupings in our bundle previously
Additional items:
– One potion requires the other potion
– a configuration rule states no more than 3 potions per backpack. So we have a little bit going on here on our product, and parent product. Specifically, we have on our standard potions feature, this configuration attribute.
– go to our standard potions feature from our backpack parent (limit of no more than three)
We know where this is associated with, but we’re going to go to the related list again and we can see a configuration attribute. It’s important to note if you’re making this configuration attribute from scratch: – click on new – choose configuration attribute (if you’ve enabled global attributes, please ignore this at this level) If a global attribute and is tied out, you’re going to have some funny behavior. We’ll talk about that in our next video, about global attributes.
Choose configuration attribute and fill out all of the information.
– Where do we want this attribute to show up?
– row order: top, middle, or bottom – column order: left, middle, or right – position on the screen: either the top or the bottom
To apply configuration attributes to all of your child products you can check this box. If you don’t see any of these on the page, then edit the page layout for this configuration attribute object. For your non global configuration attributes, you can specify the product for this configuration attribute. There are many options in Salesforce CPQ for these attributes.
In our case, it’s going to be the bundle parent (canvas backpack, even though this is also associated with the feature). For your target field if you don’t see the field listed here:
– edit your configuration attribute object
– include the field that you have created at the product option level
– For the most part that covers our configuration attribute
– close out of here because we have the configuration attribute go back to our Canvas Backpack under related and we can see all of our options.
For Salesforce Revenue Cloud Consulting, if we didn’t have these fields already created:
– select edit object,
– create the item for class
– make a new picklist value.
– make sure that all of these values are saved to a global value set
– return to object manager and make the field on quote
– make sure that there’s a pick list for class on the quote line
– Without this step it will appear functional and your data will disappear
Some best practices when using Salesforce CPQ can include making sure the values match and use global value sets to make sure that the data is always perfect. Use picklist at quote line and product option. Update the target field. Under parent product select feature and then configuration attribute. Inside of this object, update target field: – click on setup, then edit object – under fields and relationships, scroll to the bottom to get to target field – add a new value by clicking new – type in the API name of our field (class__C) – apply it to either just configuration attributes or to global attributes
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.
