Spring '20 Regression - Various search related issues observed with Product Lookup
Last updated 2021-10-12 ·Reference W-7124115 ·Reported By 21 users
Summary
Some customers may have observed search-related issues with Product Lookups post upgrade to Spring '20, the below are a few that we've observed:
1. pre-defined Filters are not respected
Pre-defined Filters are not respected when 'Product' is used as a Lookup Field, customers may see the following error:
"Value does not exist or does not match filter criteria."
2. Product Code (standard fields) and custom fields are not searchable.
Product lookup search cannot find text from searchable fields. The issue also affected custom fields with Text Area
Repro
1. pre-defined Filters are not respected
1. Create any Custom Object.
2. Create a new Lookup Field pointing to Product Entity. While creating the Lookup field add some predefined filters for Proudct.
3. Try creating a new record of the Custom Object. Observe that the Product Lookup field
2. Product Code (standard fields) and custom fields are not searchable.
1. Create a custom object (Ex: Spring20) [ Make sure you assign a tab to make it searchable]
2. Create a lookup relationship field looking up to 'Product'
3. Navigate to the 'Product' object and create a custom field with type "Text Area" [ you can call it "Product Description 1"
4. Create a Product Record and add the following info Name - VALACEPROINT-99 And Product Description 1 - VALSPAR ACE INT PRO A [ Product doesn't have to be 'Active' ]
5. Now that everything is set up, switch to LEX and create a Spring '20 custom object record | Click on the Product Lookup Relationship | Search for 'Valaceproint'
6. Note that you get results.
7. Now, repeat step 5, search for 'VALSPAR', notice that no results are returned.
Workaround
For #1, switch to Classic
For #2, for product code search, switch to classic, for Custom text area, etc., please search using the Product Name
Reported By (21)

Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.