Legacy Knowledge Base
Published Jun. 30, 2025

Unable to set the custom configurations in the price range facet

Written By

Pooja Bhambani

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Steps to reproduce:
    1. Start Liferay DXP 7.4.
    2. Create a site by using the 'speedwell' site template.
    3. Navigate to the catalog.
    4. Select the configurations of the price range facet.
    5.
    Set the configurations like the below:
    [ {'range': '[0 TO 39.99]'} \, {'range': '[40 TO 89.99]'} \, {'range': '[90 TO 189.99]'} \, {'range': '[190 TO 299.99]'} \, {'range': '[299 TO 899.99]'} \, {'range': '[900 TO *]'} ],
    6. Click Save.
    Expected Result: The price range facet must show the range defined by the user on the UI.
    Actual Result: It's saving successfully, but after the refresh, it's navigating back to the old ranges.

Environment

  • Liferay DXP 7.4
  • Commerce 4.0

Resolution

  • The observed behavior is a known issue/bug.
  • If a hotfix is required for this issue, please create a support ticket requesting a hotfix by attaching patch details.
  • Installing Fix Packs and Hotfixes on Liferay DXP will guide to installation of the hotfix in the respective environment.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base