Loading
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Work Around the V1 API Filter Limitation

          Work Around the V1 API Filter Limitation

          If you are using indexed data for product listing and search in Product Catalog Management along with the unified catalog, a known issue affects the UsedFor field in the unified catalog. Specific filter conditions fail to run because the Product Discovery V1 APIs don't recognize empty string values (for example, UsedFor eq ‘ ‘).

          Required Editions

          User Permissions Needed
          To update the Discover Products flow: Manage Flows

          In a standard unified catalog setup, you can define Service Products by setting the UsedFor field to Service Process. However, due to a limitation in the Product Discovery V1 APIs, the system currently ignores empty string filters when indexed data is enabled. As a result, when an org has Service Products (where the UsedFor field is set to “Service Process”), the system fails to filter them out during the browse catalog journey. This limitation leads to an inconsistent experience where both sellable and service-related products are shown to the user simultaneously.

          To resolve the issue, either switch to V0 APIs or maintain a separate catalog for Service Products and customize the Browse Catalog Flow to filter out Service Catalog.

          1. From Setup, in the Quick Find box, enter Flows and select it.
          2. Open the custom Discover Products flow.
          3. Click Get Catalogs element. From the Conditional Requirements dropdown list, select All Conditions are Met (AND). Add the condition, select Catalog Type as the Field, Does Not Equal as the Operator, and Service Process as the Value.
          4. Click Save as New Flow.
          5. Enter a flow label and a flow API name.
          6. Save and activate the flow.

            The indexing feature may not work as expected if the Product Variants org preference is turned on and a large number of product variants are added. If indexing fails, turn off the Product Variants org preference. This workaround is recommended for larger orgs, smaller orgs are less likely to encounter this issue.

           
          Loading
          Salesforce Help | Article