Legacy Knowledge Base
Published Jun. 30, 2025

400 Bad Response When Filtering Using the API on Custom Fields

Written By

Ally McGill

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 filtering using the API on a custom field of type "long integer" (for example: customID eq '123'), I get a bad request response; but when I use the same syntax on an out-of-the-box field with type "long integer", information is returned as expected. 

Environment

  • Liferay Quarterly Release

Resolution

  • The current expected syntax is:
    • Custom Fields use unquoted numbers (for example: customID eq 123)
    • OOTB Fields use quoted numbers (for example: ID eq '123')

 

Did this article resolve your issue ?

Legacy Knowledge Base