Ask Search:
Kris ZwetzigKris Zwetzig 

configuration attributes "apply to product options" field

I am having some issues wrapping my head around the functionality for configuration attributes.
There is a field on the configuration attribute record called "Apply To Product Options"
 
From my reading my understanding is this allows the configuration to pass its value to all of the product options, but it seems to not be functioning as i would expect. I found that there was a bug that was fixed in a recent update but even after updating my sandbox i still cant get this to work.
 
I have 4 configuration attributes on a particular feature, and i want to pass those values to the product option so i can use them in a formula field, and then pass the formula value to a price rule to drive the quantity. but i cant seem to make this work.
 
Any direction/advice on what i could be missing? or anyone have an understanding of how this "Apply to product options" field applies the attribute value to the product option records?
Best Answer chosen by Kris Zwetzig
Divyesh PatelDivyesh Patel
Kris - The selected (config attribute) value is passed to matching filed of product options (if Apply to Product Options is selected) but isn't visible on the user iterface/product selection screen until you click save button on the configure screen. I know you expect it to be shown real-time immediately but that's not the standard behavior.

Once you save the configuration, you should be able to see the selected config attribute value against the matching field on all the quote lines in the quote line editor  (provided you have added the matching field also on the quote line object and have added it to the field set). 

All Answers

Justin morimotoJustin morimoto
Hello,

Apply the configuration attribute’s value to all matching fields in your bundle’s product options. When this field is not selected, Salesforce CPQ applies the value to only matching fields in the bundle parent.

What version is the instance currently on?
Kris ZwetzigKris Zwetzig

I upgraded to 212.14.7 in my sandbox. options are being selected and shown via a product selection rule based on the same configuration attribute. i added the product option field shown below to the edit lines field set on the product option object so i could see the field in the configurator.  my expectation was that when i populated the configuration attributes value that is being displayed on the feature, that i would see the field populate in the option's within that feature


what specifically qualifies as a "matching field" ?

Heres my configuration attribute

User-added image

Heres the target field value mapping to product option field

Target Field
heres my product option field

Product Option field

 

 

 

Divyesh PatelDivyesh Patel
Kris - The selected (config attribute) value is passed to matching filed of product options (if Apply to Product Options is selected) but isn't visible on the user iterface/product selection screen until you click save button on the configure screen. I know you expect it to be shown real-time immediately but that's not the standard behavior.

Once you save the configuration, you should be able to see the selected config attribute value against the matching field on all the quote lines in the quote line editor  (provided you have added the matching field also on the quote line object and have added it to the field set). 
This was selected as the best answer
Kris ZwetzigKris Zwetzig

Thanks Divyesh, that was a major roadblock that was preventing me from accomplishing my goal.

Since the value is being passed from the configuration attribute to Quote line now i was able to create a formula field and a price rule on the value to populate quantity.

Nathan BoydNathan Boyd

I have followed these steps but am not getting the results you are Kris.

I added the field for the Configuration Attribte to the Product, Product Option, and Quote Line. Set a Price Rule that targets this field but my quantity is not changing.

My setup is I have a nested bundle; Grand-Parent > Parent 'A' > Child 'C' I have a Configuration Attribute on the Grand-Parent Product (Number of Employees), based off the value entered here the quantity of a single Child Product, 'C'.

Listing 'A' and 'C' to show that I have many Products at the Parent and Child levels. My pricing model is we have different products, A, B, C. And within those Products we have Packages, Std., Prem., Ult. Each package is made up of several Products. Within those Packages I need to target the main Product Configuration Attribute and update the quantity of a single Package product.

Thanks in advance for any assistance!

Kris ZwetzigKris Zwetzig

Hi Nathan, I never actually came to a solution that allowed me to update quantity of any product based on the value of a configuration attribute while still in the configurator. I was only able to pass a configuration attribute from the product option to the quote line record when a record was saved, and then execute a price rule on this value at the quote line.

We are a current prmier plus admin customer, i went through the acellerator for product and pricing rules, and basically came to the conclusion that you are not currently able to do this within the configurator.

The solution presents some challanges as the sales reps (rightfully) assume that the quantity would be updated in the configurator during configuration. and any input they could provide on quantity would then be overriden by the price rule.

i did not end up implementing this solution, instead it made more sense to just make the sales rep populate quantities and have control over configuration as they saw fit.

Hope that helps answer your question, if not let me know i would be happy to jump on a call with you.
There arent many CPQ experts out there at this point from what i can tell....

Nathan BoydNathan Boyd
Hey Kris,
From the price rule I created I was only able to update the quantities for all products added during configuration. It doesn't seem like there is a way to target a single product with a price rule. In my scenerio the price rule did execute when price conditions were met, just for all products. The 'Product' field on the details of the rule is misleading..
Kris ZwetzigKris Zwetzig

You would have to filter the products down using a lookup query.

If you want to update 1 product's quantity i would just do a lookup query where you compare the lookup field to a static value.

Depending on your use case it might make sense to have some sort of category field that segments the product data, and compare the lookup field value to that category so that the rule would be repeatable across multiple bundles / products.

 

User-added image

Kris ZwetzigKris Zwetzig
Yes i agree, most of everything in Salesforce CPQ is miseleading.... I have spent months and many hours learning this tool, just waiting till my next dreamforce to take the exam at a discount.
Kris ZwetzigKris Zwetzig

If you are making the change based on a value on the quote line itself you can also just use a price condition.

In this example i am only executing this action on quote lines that have a product family not equal to "Non Discount" you could do the same thing with a specific product value

User-added image

Chris ChingChris Ching
Just to also provide some other options available, please take a look at Product Rules. This also can help shape what users do in the configuration attribute screen. You can validate, select, filter and alert users based on a set of criteria. Using product rules allows you to guide them through configuring a specifc configurable product. So just to give an example, if they aren't allow to go 100 > Qunatity, you can have a message flash that they aren't allowed to do this, or validate against them saving it.
Dennis PalmerDennis Palmer
Another note on this one:  Apply to Product Options seems to apply the values to options only at save.  It may seem like it's only the display but that's only because product rules fire correctly on first configuration based on config attribute values.  When you have a lookup price rule that is based on lookup queries on fields set by configuration attributes (with apply to product options), the lookup does not fire correctly and the actions don't fire.

Similarly, if your price rule sets a field to a formula that references a field set by a configuration attribute (with apply to product options), the action does not set the value correctly.