Salesforce CPQ: More on Configuration Attributes

We previously wrote a blog post on troubleshooting Configuration Attributes, and now it's time to update our list.  
Sometimes you need to update the values on a picklist field that is restricted to the values defined in the value set and forget to update them on all objects involved. So let's say you've updated the field on the Quote Line by removing one value but didn't update it on the Product Option. And these fields are targeted by a Configuration attribute. 

Suppose you select a value for the Configuration Attribute that exists only in the value set of the Product Option and try to save the bundle configuration. In that case, Salesforce CPQ will stop you from doing so. An error message invoking "bad value" will appear, preventing you from saving the bundle configuration:

That's why the values in the value sets need to be aligned. Kindly note that if the picklist is not restricted to the values defined in the value set, it will allow you to save the bundle configuration, and the value coming from the Product Option will be successfully saved in the related quote line twin field.

Another scenario is when admins need to display the value from a field targeted by a Configuration Attribute in the quote output document. The related field was initially created only on the Product Option. In this case, creating the same field on the Quote Line object is necessary. But it goes without saying that the twin field on the Quote Line is mandatory because it is used to store permanently the value entered via the Configuration Attribute. If you fail to create the field on both these objects, your attribute isn't going to work as expected.  

One last thing, if you have a Configuration Attribute that is currently on a bundle and you want to  "reuse" it for a different bundle - you'll have to create a second Configuration Attribute.