Search Filters

by Community Manager on ‎08-12-2015 03:03 PM - edited on ‎11-09-2016 04:04 PM by Community Manager


The Quote Line Editor's Search Filter allows you to filter a Quote's Products, Assets or Subscriptions based on their field values - for instance, you could search for all Products where the Product Name field contains "Monitor". Salesforce CPQ allows you to search Product Code, Product Name, Product Family and Product Description by default, but users can add standard or custom fields to any search filter.



Search Filter Field Definitions

Users should create a new Search Filter object and set its fields to target to the object/field they want to search. For instance, you could search the values of the Industry field on the Quote object. An "Industry" search filter will then appear in the Quote Line Editor.


search filters.png

  • Target Object: Select the Object containing the field you want to search. In this case, Industry is on the Product object.
  • Target Field: Select the field you want to search. 
  • Operator: Select the logic operator that you want to run against your filter input. In this case, we want to see whether the Industry field contains a certain text value, so the field value should be Contains.
  • Display Order: This number will determine where the filter is ordered relative to other Search Filters on the Quote Line Editor's Search Filter box. 
  • Filter Value: If desired, add a text value that will be automatically searched before the user inputs any text. For example, your search filter could target the Monitor Display Type field on Products - if you only want your sales reps to search for certain monitors within all IPS monitors, you could enter "IPS" in this field.
  • Hidden: Select to hide this filter from the UI. Hidden filters still contribute to search queries. You could select this field in combination with an established Filter Value if you do not want sales reps to know that search results are already limited.
  • Action: (Optional) Search filters can be used with Custom Actions. For example, you could have an "Add Hardware" Custom Action that filters Products on the Search Filter criteria Product Family = Hardware. The value entered in this field will relate the Search Filter to an existing Custom Action - users can then select that Custom Action in the Quote Line Editor to automatically filter Products.

Search Filter Advanced Information Definitions

Search Filter Advanced Information fields can create dynamic Search Filters. For example, a sales rep may want to filter Products based on the Country they're quoting to. 



Tip: Be careful when creating Search filters because checkboxes cannot contain Null values. Therefore, you must always filter on either True or False. It is recommended to use a None/Yes/No picklist even if such a picklist is populated behind the scenes via a Workflow Rule.

Tip: Best Practice for filtering Product Search results: Use the "equals" operator (instead of the "contains" operator). Providing your filter with a list of comma-separated values will cause your search to perform a logical OR between each value in the list.


by sshapiro
on ‎07-05-2016 10:26 AM

Where is there information on the Search Filter object, including the Advanced Information section of that object?

by J_Dunn
on ‎12-06-2016 09:03 AM

Salesforce CPQ allows you to search Product Code, Product Name, Product Family and Product Description by default, but users can add standard or custom fields to any search filter.


How I am able to use custom fields?  When i select Product as my target object the only fields available to choose from are Code, Name, Family & Description.



by Bine12
on ‎02-23-2017 12:50 PM

When I add a custom filter the whole filter section disappears from the layout and it does not filter. Any ideas?

on ‎03-30-2017 12:09 PM

Why oh why did you remove the "Close Search Filter By Default" checkbox from the package settings?  

by Paul_Fury
on ‎05-10-2017 10:35 PM

Please bring back the ability to show the filter by default.  

by nathanspiwak
on ‎06-27-2017 12:30 PM

We have custom fields Start Date and End Date on the Product object. I'm trying to filter to only have Producst within the selected date range. I've created a Start Date filter (greater or equals) and End Date filter (less or equals), but it's not working. It still shows records that are outside the date range. Are each filter combined using AND, meaning the product's Start Date has to be great or equal x date AND the product's End Date has to be less or equal x date? Or are the two filters combined using OR? Or is there another reason why the filters might not work as expected? 

on ‎06-27-2017 12:55 PM

It should be AND.  Reasons why this might not work:


1. Target Field does not have the correct Field API name.

2. Target Object is set to something other than Product.

3. Greater or Equals, Less or Equals needs to be swapped with each other on the two filters.

by Nikita_Che
on ‎08-29-2017 12:08 PM

@Bine12 you can re-add custom search filters, and they should work in the same way. If you have dependencies between filter values on your Product object, dependencies will remain in the new search filters. But I am sure you have implemented this already long ago. Robot Happy 

by KevinW
on ‎11-02-2017 12:26 AM

STEP 1: "Users should create a new Search Filter object" ?


There already is a SBQQ__SearchfFilter__c Object.

by KevinW
on ‎11-02-2017 12:44 AM

Why are we creating " Industry field on the Quote object" then we create a filter which refreences the Product Object? That doesn't seem to make sense. Do we need to add teh Industry field/options to the Quote object?

by derekkipps
on ‎01-16-2018 10:35 AM

@nathanspiwak I am also struggling with dates as Search Filters. Did you ever get this to work? I know search filters do not handle NULLs well. I've only got a date filter (e.g. Earliest_Available__c on Product2) to compare to a field on quote (e.g. Customer_Date_Needed__c on SBQQ__Quote__c). 99% of the time the heading shows in the filter but not the date picker. And 100% of the time I've not been able to show a different data set when changing dates, or greater than/less than operators.