Legacy Knowledge Base
Published Jun. 30, 2025

Custom Facet displays encoded term values

Written By

Daniel Carrillo Broeder

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

  • After setting up a custom facet on a search page, it only shows encoded values.
  • The custom facet is configured with an Aggregation Field that includes a sortable search field.

Environment

  • DXP 7.2 - Liferay Connector to Elasticsearch 7 v3.4.0+
  • DXP 7.3 U7+
  • DXP 7.4 U27+
  • Quarterly Releases

Resolution

  • This behavior is expected after this Breaking Change was reported.
  • You will need to modify the Aggregation field adding .keyword_lowercase at the end :
  • dmFieldArray.ddm__keyword__12345__example_en_US.ddmFieldValueKeyword_en_US_String_sortable.keyword_lowercase
  • There is a limitation preventing this configuration, so we encourage you to contact the support service for further assistance if you encounter this issue.
  • This limitation does not affect portals with the "Enable Legacy Dynamic Data Mapping Index Fields" configuration enabled, but you will still need to add .keyword_lowercase:
  • ddm__keyword__12345__example_es_ES_String_sortable.keyword_lowercase

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base