Filter Rules and Dynamic Bundles in Salesforce CPQ

A filter rule is a product rule where the Type field is set to Filter. Filter rules use configuration rules to target a bundle feature and actions to determine whether certain options appear when users configure a bundle. For example, let’s say your company sells an IT security bundle and you regularly update your product offering with new security products. In this case, it’s easier to create a bundle that can contain any security product rather than constantly updating the bundle’s options based on your offering.

We call this type of bundle a dynamic bundle. To enable this setup, set a feature’s Option Selection Method field to Dynamic.

Actions for filter rules need Filter Field, Operator, and Filter Value fields to determine the product or products you want to filter. If you target a field in your Product Search sidebar, Salesforce CPQ populates that field’s value with the value you choose in your action. From here, you can use the action’s type to choose whether sales reps can remove that value and thus the filter. A type set to Default Filter means that the filtering persists even if you remove the filtered value from the Product Search sidebar. A type set to Optional Filter means that Salesforce CPQ removes the filter logic when you remove the filtered value from the sidebar.

Your action’s filter field evaluates only fields on the product option. To evaluate a product field, make an exact duplicate of that field on the product option and use it for your filter field instead.

When you contract a dynamic bundle, the resulting asset, subscription, or contract line item has a value in its Dynamic Option ID field. The dynamic option ID represents a combination of the feature ID and product ID, which lets you identify the feature and product associated with the dynamic bundle.

You can then set your configuration rule to target the bundle and select the feature you want to filter from.

Because you’re not using Error Conditions, you can leave your filter rule’s Conditions Met and Advanced Conditions fields blank.

Dynamic bundle custom fields aren’t populated with values until a corresponding entry for the field is added to the Search Results field set. For this reason, these fields appear when you’re looking up products to add to the quote.

Important If Percent of Total is added as an option to Dynamic features, that product’s reconfiguration isn’t supported on the product configuration page.