Salesforce CPQ: Twin Fields

Two of the most potent and helpful out-of-the-box tools in CPQ are Price rules and Twin fields. These can help you achieve precise calculations and manage your data in a single place. Today we'll discuss twin fields. Salesforce CPQ passes field values from one object to another object when the latter is created if:

► the fields are editable;
► they have matching API names;
► they have matching field types.

Important to remember: Standard fields cannot be mapped between objects. Note that the Product Code field has different API names on the Product object (ProductCode) and on the Product Option object (SBQQ__ProductCode__c). However, there is a functionality built-in and these fields are still matching as though they are twins.

Now, suppose you've got a field on the Product Object that you want to see on the Quote Line as well. What you have to do is to go and create a field with the same API name and of the same type. Et voila! Salesforce CPQ does all the magic for you!

►One-Way Mapping

The principle behind One-Way Mapping is the following: the Objects in first column of the table below transfer their field values to fields with matching types and matching API names to the objects from the second column.

► Mapping in the Configurator

When a bundle is configured, objects in Column 1 transfer their values to the emerging new quote lines. When you access the configurator to reconfigure the bundle, Salesforce CPQ sets product options and configuration attribute values based on matching field values from their related quote lines.

Note: If you mark a bundle a Favorite and then add that favorite bundle to the quote line editor, it won't seize any twin field values.