Legacy Knowledge Base
Published Jun. 30, 2025

Commerce: checkout address drop-down not showing all addresses

Written By

Sorin Pop

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

  • When user checks out, in the shipping address drop-down some addresses cannot be found

Environment

  • DXP 7.3 SP1

Resolution

  • You probably have a lot of addresses (more than 10 000) belonging to that account
  • The issue is due to some limits applied for the Elasticsearch server, which tell that this server can return a maximum of 10 000 results. The addresses in the drop-down (at the checkout) are retrieved from Elasticsearch, and if there are more than 10 000 addresses for the current account, not all of them will be retrieved and listed in the drop-down.
     
  • Therefore we suggest to either:
  1. modify the business use case so that you create maximum 10 000 addresses for an account, or
  2. increase this limit to a size larger than the number of addresses in order to ensure all are returned (e.g. 20 000). This you can do by setting 

 

index.search.limit=20000

 
in portal-ext and also setting Elasticsearch parameter index.max_result_window to 20 000 as per this article
The side effect of this could be delays in the search, as more data is being transferred.
 
(in 7.4 this part has been extensively refactored and seems to works better, these limits don't need to be raised)

 

Did this article resolve your issue ?

Legacy Knowledge Base